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

"/v1/apps/scale" always returns 204 even in failure or bad request

    Details

      Description

      Scaling to negative instances:

      $ http POST http://localhost:8080/v1/apps/scale id=eat-legos instances=-3
      

      makes Marathon happily return a 204:

      Jan 07, 2014 11:36:24 AM mesosphere.marathon.MarathonScheduler mesosphere$marathon$MarathonScheduler$$scale
      INFO: Scaling eat-legos from 0 down to -3 instances
      

      Something in 4XX is more reasonable, either 400 or 403.

      If Marathon is unable to scale the app for any reason, it should also return a non-2XX code to let the client know the scaling did not happen. The current implementation always responds with a 204, which means the client has to re-request the app to determine if the scale request was successful.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: