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

Resident task rolling restart with suspended tasks has surprising behavior

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Cannot Reproduce
    • Affects Version/s: Marathon 1.1.5, Marathon 1.5.0
    • Fix Version/s: None
    • Component/s: Storage Volumes
    • Labels:
      None

      Description

      If a resident task has some app instances in a Suspended state, and a rolling restart of the app is initiated, The Suspended tasks can be brought into the restart instead of the ones that are already active, effectively shuffling which reservations are active.

      Expected behavior:
      Only non-suspended reservations are the ones used during a rolling restart.

      Actual behavior:
      ANY reservation (even suspended ones) are used to fulfill the app needs in a non-deterministic manner.

      At the very least this should be documented, ideally it should be somewhat deterministic.

        Attachments

          Activity

            People

            • Assignee:
              ivanchernetsky Ivan Chernetsky
              Reporter:
              drcrallen drcrallen
              Team:
              Orchestration Team
              Watchers:
              drcrallen, Ivan Chernetsky
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: