You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2013/10/09 03:26:42 UTC
[jira] [Resolved] (MESOS-110) Slave Recovery: A slave restart
should not restart tasks
[ https://issues.apache.org/jira/browse/MESOS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone resolved MESOS-110.
------------------------------
Resolution: Fixed
> Slave Recovery: A slave restart should not restart tasks
> --------------------------------------------------------
>
> Key: MESOS-110
> URL: https://issues.apache.org/jira/browse/MESOS-110
> Project: Mesos
> Issue Type: Story
> Components: framework, master, slave
> Reporter: Rob Benson
> Assignee: Vinod Kone
> Priority: Blocker
> Fix For: 0.14.0
>
>
> Running a long-lived service on Mesos has a significant drawback right now in that Mesos build deploys restart your tasks. This could lead to nontrivial outages for services that have a high warm-up time. Basically everything would need a graceful restart mechanism that basically allows a shutdown/restart with a new version of the code.
> With this feature intended(e.g., deploys) or unintended slave restarts (e.g., crashes) will not kill the tasks underneath. When the slave restarts it recovers by reconnecting with the old live executors/tasks.
--
This message was sent by Atlassian JIRA
(v6.1#6144)