mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Harutyunyan (JIRA)" <>
Subject [jira] [Updated] (MESOS-3583) Introduce sessions in HTTP Scheduler API Subscribed Responses
Date Mon, 01 Feb 2016 19:18:40 GMT


Artem Harutyunyan updated MESOS-3583:
    Sprint:   (was: Mesosphere Sprint 28)

> Introduce sessions in HTTP Scheduler API Subscribed Responses
> -------------------------------------------------------------
>                 Key: MESOS-3583
>                 URL:
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Anand Mazumdar
>              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.

This message was sent by Atlassian JIRA

View raw message