[MESOS-3583] Introduce stream IDs in HTTP Scheduler API

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.28.0
• Labels: mesosphere tech-debt
• Epic Link: Scheduler API v1 improvements
• Sprint: Mesosphere Sprint 30
• Story Points: 5
• Assignee: Greg Mann
• Reporter: Anand Mazumdar
• Shepherd: Vinod Kone
• Created: 05/Oct/15 17:47
• Updated: 26/Nov/18 12:20
• Resolved: 26/Nov/18 12:20

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.

Issue Links

• is blocked by: MESOS-4573 Design doc for scheduler HTTP Stream IDs