Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-8146

backoffSeconds and backoffFactor have no effect for resident apps

    Details

      Description

      Given the following example application on DC/OS 1.11, we observed that the settings "backoffFactor" and "backoffSeconds" have no effect when volumes are involved.

      {
        "id": "/reservation-availability",
        "backoffFactor": 1,
        "backoffSeconds": 3600,
        "cmd": "sleep 10\nexit 1",
        "container": {
          "type": "DOCKER",
          "volumes": [
            {
              "persistent": {
                "type": "root",
                "size": 32,
                "constraints": []
              },
              "mode": "RW",
              "containerPath": "test"
            },
            {
              "containerPath": "/test",
              "hostPath": "test",
              "mode": "RW"
            }
          ],
          "docker": {
            "image": "alpine"
          }
        },
        "cpus": 0.01,
        "disk": 0,
        "instances": 1,
        "maxLaunchDelaySeconds": 3600,
        "mem": 64,
        "gpus": 0,
        "networks": [
          {
            "mode": "host"
          }
        ]
      }
      

      We see the following relaunching behavior:

      The relaunching never appears to stop.

      If you remove the persistent volumes from the app definition (delete the old one, and then re-create it), then the back off configuration works as documented.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                tharper Tim Harper
                Team:
                Orchestration Team
                Watchers:
                Karsten Jeschkies, Nikita Melkozerov (Inactive), Tim Harper
              • Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: