Anand Mazumdar created MESOS-3583: ------------------------------------- Summary: Introduce sessions in HTTP API Subscribed Responses Key: MESOS-3583 URL: https://issues.apache.org/jira/browse/MESOS-3583 Project: Mesos Issue Type: Task Reporter: Anand Mazumdar
Currently, the HTTP 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)