[
https://issues.apache.org/jira/browse/MESOS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176277#comment-15176277
]
Greg Mann commented on MESOS-3583:
----------------------------------
Review requests here:
https://reviews.apache.org/r/44278/
https://reviews.apache.org/r/44279/
> Introduce stream IDs in HTTP Scheduler API
> ------------------------------------------
>
> Key: MESOS-3583
> URL: https://issues.apache.org/jira/browse/MESOS-3583
> Project: Mesos
> Issue Type: Task
> Reporter: Anand Mazumdar
> Assignee: Greg Mann
> Labels: mesosphere, tech-debt
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
