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

Containerizers should persist their own recovery state.

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

    Details

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

      Description

      In the current containerizer refactor (and previous process_isolator and cgroups_isolator) the forked executor pid is persisted by the MesosContainerizer but recovered with the rest of the slave state. This coupling is undesirable as containerizer implementations may or may not use the pid for recovery and may require additional, specific state for recovery.

      Instead each containerizer implementation should manage persistence of whatever state they require for recovery.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              idownes Ian Downes

              Dates

              • Created:
                Updated:

                Issue deployment