Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-8636

Master should store `completed` frameworks for lifecycle enforcement separately from that for webUI and endpoints

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Reviewable
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Currently the master stores the history of completed frameworks in a map with the full historical data of the framework.

      struct Frameworks 
      {
        BoundedHashMap<FrameworkID, process::Owned<Framework>> completed;
      }
      

      This map serves the purposes of

      1. Rejecting frameworks from reregistering if they have previously marked as completed.
      2. Displaying the history of this framework (i.e., its tasks) via webUI and endpoints.

      However because the full framework object is large, it could be prohibitively expensive to keep a long history for its relatively low importance.

      However for 1, we only need to persist the framework ID and keeping a longer history is essential to the integrity of the cluster.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              fiu Xudong Ni
              Reporter:
              xujyan Yan Xu
              Shepherd:
              Yan Xu

              Dates

              • Created:
                Updated:

                Issue deployment