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

why marathon account instance number into Version?

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Medium
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Orchestration
    • Labels:

      Description

      Lets say I have an app which first has 5 instances running, and then, I'd like to scale it to 3, ok, marathon generates a new Version with only instances changed.

      As a end user, ok, it's fine, because I see there are 3 instances and all of them has the same Version, that's make me happy, no surprise.

      However, if I scale my app from 1 to 8, ok, it does surprise me, it says there are 2 Versions instances, 1 in version 1 and 7 in version 2.

      See instances list as below.

      That's definitely not a good idea I think, from an end user point of view.

      It just says my application going to sane, inconsistent state.

      I think we should kick instance out of Version.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                chengweiv5 Chengwei Yang
                Team:
                Orchestration Team
                Watchers:
                Jason Gilanfarr (Inactive), Matthias Eichstedt
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: