You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Klaus Ma (JIRA)" <ji...@apache.org> on 2015/11/06 15:03:27 UTC
[jira] [Updated] (MESOS-3420) Resolve shutdown semantics for
Machine/Down
[ https://issues.apache.org/jira/browse/MESOS-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Klaus Ma updated MESOS-3420:
----------------------------
Target Version/s: 0.27.0 (was: 0.26.0)
> Resolve shutdown semantics for Machine/Down
> -------------------------------------------
>
> Key: MESOS-3420
> URL: https://issues.apache.org/jira/browse/MESOS-3420
> Project: Mesos
> Issue Type: Task
> Reporter: Joris Van Remoortere
> Assignee: Klaus Ma
> Labels: maintenance, mesosphere
>
> When an operator uses the {{machine/down}} endpoint, the master sends a shutdown message to the agent.
> We need to discuss and resolve the semantics that we want regarding the operators and frameworks knowing when their tasks are terminated.
> One option is to explicitly remove the agent from the master which will send the {{TASK_LOST}} updates and {{SlaveLostMessage}} directly from the master. The concern around this is that during a network partition, or if the agent was down at the time, that these tasks could still be running.
> This is a general problem related to task life-times being dissociated with that life-time of the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)