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/08/16 20:45:23 UTC
[jira] [Updated] (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 updated MESOS-110:
-----------------------------

    Component/s: slave
                 master
    Description: 
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.

  was: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. 

        Summary: Slave Recovery: A slave restart should not restart tasks  (was: Mesos deploys should not restart tasks)
    
> 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: New Feature
>          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