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

We need to better document behaviour of PUT /v2/apps/{appid}

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Low
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: DC/OS 1.11.3
    • Component/s: Docs
    • Labels:
      None

      Description

      The documentation for PUT /v2/apps/

      {appid} (https://mesosphere.github.io/marathon/docs/rest-api.html#put-/v2/apps/{appid}

      ) mentions that "Currently running tasks are restarted" but according to my understanding that is not always true because its smarter than always restarting the current tasks. Exceptions being(as per my understanding):
      1) When scaling up the app without changing anything else
      2) When doing a PUT with exact same add definition

      It would be useful to document the exceptions in the documentation

        Attachments

          Activity

            People

            • Assignee:
              nikitamelkozerov Nikita Melkozerov
              Reporter:
              GitHub_surdy Harpreet Singh Gulati (Inactive)
              Team:
              Orchestration Team
              Watchers:
              Chmielewski, Jason Gilanfarr (Inactive), Matthias Eichstedt, Srikanth Viswanathan
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: