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

Containerizers should persist their own recovery state.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • containerization
    • 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

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MESOS-1328 Slave should not rely on a checkpointed forkedPid

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              idownes Ian Downes
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: