You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Jordan Curzon (JIRA)" <ji...@apache.org> on 2013/09/25 20:36:03 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13777878#comment-13777878 ] 

Jordan Curzon commented on MESOS-110:
-------------------------------------

Has there been any more work on this?
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira