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

Indicate repeated deployment failures (flapping instances)

    Details

    • Type: Task
    • Status: Open
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Orchestration
    • Labels:

      Description

      Very often an app goes into a flapping state, where it repeatedly fails to launch and is restarted over and over by Marathon.

      The status will flip every few seconds between WAITING, STAGING, RUNNING.
      If you look at the UI for a moment, everything might look OK. There is no indication that your app is trapped in a failure cycle.

      Marathon should recognise a repeated failure loop and signal specifically that this is happening.
      Example: Status could read MULTIPLE FAILURES (N) where N is the number of failures since the last stable state. Or, MULTIPLE FAILURES (N min) where N is the number of minutes the app has been in a non-Running state.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              aaron Aaron Bell (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: