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

Investigate self-hosting Mesos processes

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Accepted
    • Major
    • Resolution: Unresolved
    • None
    • None
    • master

    Description

      Right now, Mesos master and slave nodes are managed differently: they use different binaries and startup scripts and require different ops procedures. Some of this asymmetric is essential, but perhaps not all of it is. If Mesos supported a concept of "persistent tasks" (see MESOS-3545), it might be possible to implement the Mesos master as such a task – this might help unify the ops procedures between a master and a slave.

      Attachments

        Issue Links

          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MESOS-3545 Investigate restoring tasks/executors after machine reboot.

          • Major - Major loss of function.
          • Accepted
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-3548 Investigate federations of Mesos masters

          • Major - Major loss of function.
          • Accepted

          Activity

            People

              Unassigned Unassigned
              neilc Neil Conway
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: