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

Introduce stream IDs in HTTP Scheduler API

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.28.0
    • Component/s: None

      Description

      Currently, the HTTP Scheduler API has no concept of Sessions aka SessionID or a TokenID. This is useful in some failure scenarios. As of now, if a framework fails over and then subscribes again with the same FrameworkID with the force option set, the Mesos master would subscribe it.

      If the previous instance of the framework/scheduler tries to send a Call , e.g. Call::KILL with the same previous FrameworkID set, it would be still accepted by the master leading to erroneously killing a task.

      This is possible because we do not have a way currently of distinguishing connections. It used to work in the previous driver implementation due to the master also performing a UPID check to verify if they matched and only then allowing the call. Following the design process, we will implemented "stream IDs" for Mesos HTTP schedulers; each ID will be associated with a single subscription connection, and the scheduler must include it as a header in all non-subscribe calls sent to the master.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                greggomann Greg Mann
                Reporter:
                anandmazumdar Anand Mazumdar
                Shepherd:
                Vinod Kone
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: