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

Support idempotent framework registration

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Right now when a framework registers/subscribes, the master assigns a framework ID to it and send it back so the framework can use it to tear itself down on Mesos when it's done. However if the framework fails to receive it (e.g., it fails over before it receives the ID), it doesn't have a way to do the teardown or failover.

      One apparent solution would be to allow the frameworks to supply the framework IDs themselves but it may be easier for backwards compatibility to come up with a new framework supplied "unique name/handle" concept to allow the framework to identify itself.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              xujyan Yan Xu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: