Uploaded image for project: 'DC/OS'
  1. DC/OS
  2. DCOS_OSS-4625

Make Metronome more conservative about creating new framework ids

    Details

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

      Description

      In MARATHON-8420 we made Marathon more conservative about creating new framework ids, having it refuse to do so if any instances exist. Since Metronome is about one-off jobs, it does not keep instances around, they're expunged as soon as they're done launching.

      We propose to update the framework connection logic to make the signal for allowing the creation of a new framework id to be configurable, so that Metronome can instead check to see if any jobs are defined, and only allow the creation of a new framework id if a successful empty response is returned.

      Acceptance Criteria

      Given a fresh instance of Metronome with no jobs
      When I launch it
      Then a frameworkId should be created and stored
      When I create a job and delete the frameworkId record
      And I relaunch Metronome
      Then Metronome should refuse to create a new frameworkId

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tharper Tim Harper
              Team:
              Orchestration Team
              Watchers:
              Tim Harper
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: