[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-issues
Subject:    [jira] [Commented] (MESOS-3545) Investigate restoring tasks/executors after machine reboot.
From:       "Megha (JIRA)" <jira () apache ! org>
Date:       2015-10-30 18:25:27
Message-ID: JIRA.12901181.1443483011000.110657.1446229527877 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/MESOS-3545?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=14983016#comment-14983016 ] 

Megha commented on MESOS-3545:
------------------------------

Thanks Neil, shared it on the dev mailing list last Friday.

> Investigate restoring tasks/executors after machine reboot.
> -----------------------------------------------------------
> 
> Key: MESOS-3545
> URL: https://issues.apache.org/jira/browse/MESOS-3545
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Benjamin Hindman
> Labels: mesosphere
> 
> If a task/executor is restartable (see MESOS-3544) it might make sense to force an \
> agent to restart these tasks/executors _before_ after a machine reboot in the event \
> that the machine is network partitioned away from the master (or the master has \
> failed) but we'd like to get these services running again. Assuming the agent(s) \
> running on the machine has not been disconnected from the master for longer than \
> the master's agent re-registration timeout the agent should be able to re-register \
> (i.e., after a network partition is resolved) without a problem. However, in the \
> same way that a framework would be interested in knowing that it's tasks/executors \
> were restarted we'd want to send something like a TASK_RESTARTED status update.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread]