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

/v2/tasks returns tasks in random order

    Details

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

      Description

      (this is an old release - 0.7.5 - but I haven't seen any commits that would fix it in later releases).

      Despite being fine for months, yesterday our 3-node marathon cluster started returning tasks in a different
      order every other time it was polled. This caused havoc on the service discovery layer, as the different order caused constant haproxy reloads on all slaves and gateways.

      is there a 'contract' that this order should be maintained, or should discovery solutions that use this information assume it will be random and sort accordingly?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              GitHub_rasputnik Dick Davies (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: