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

Should modifying "instances" update AppDefinition "version"?

    Details

    • Type: Task
    • Status: Resolved
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Say you want to create a new app:

      curl -X PUT -H 'Content-type: application/json' \
        http://localhost:8080/v2/apps/sleepy_time -d \
        '{"cmd": "sleep 500", "cpus": 1, "mem": 16, "instances": 2}'
      

      And once you've launched it you want to scale it to more instances:

      curl -X PUT -H 'Content-type: application/json' \
        http://localhost:8080/v2/apps/sleepy_time -d \
        '{"cmd": "sleep 500", "cpus": 1, "mem": 16, "instances": 5}'
      

      The only attribute that changed was "instances", but all tasks launched after the second PUT will have a different "version" than those launched before the second PUT.

      • Should "instances" be a member of AppDefinition? It actually means, "the number of tasks to run with the other attributes of this AppDefintion"; it has no effect on the tasks themselves.

        Attachments

          Activity

            People

            • Assignee:
              GitHub_ConnorDoyle Connor Doyle (Inactive)
              Reporter:
              GitHub_ssorallen Ross Allen (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: