[jira] [Commented] (MESOS-1739) Allow slave reconfiguration on restart

["Deshi Xiao (JIRA)" <ji...@apache.org>]

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

Deshi Xiao commented on MESOS-1739:
-----------------------------------

log adam's describe to understand the issue's background

{quote}
bq. Adam B 7 hours, 21 minutes ago (五月 18, 2016, 7:18 p.m.)
Desired behavior: Operator can kill a slave process and restart it with new --attributes. Existing tasks will continue to run. No TASK_LOST or SLAVE_LOST message is sent. The slaveId remains the same. Outstanding offers from that slave will be rescinded, and those offers will be remade with the updated attributes.
Current behavior 1: Operator shuts down a slave process, and restarts with --recover=cleanup, which kills all its tasks, clears the work_dir, and notifies the master that the old slaveId is "shutdown" and will never be reused again (SLAVE_LOST, offers rescinded, TASK_KILLED/LOST). Operator then restarts the slave with new --attributes, it gets a new slaveId, and new offers will be made with the new slaveId and updated attributes.
Current behavior 2: Slave process dies/killed and tries to restart with new --attributes. Errors on recovery.
Current behavior 3: Slave process dies/killed and doesn't reregister in slave_ping_timeout*max_slave_ping_timeouts (90s). Master considers it gone, sends SLAVE_LOST, TASK_LOST. Future attempts to reregister with the same slaveId fail. Slave must be cleaned up (tasks killed, work_dir removed) so it can register with a new slaveId (and new attributes).
{quote}

> Allow slave reconfiguration on restart
> --------------------------------------
>
>                 Key: MESOS-1739
>                 URL: https://issues.apache.org/jira/browse/MESOS-1739
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Patrick Reilly
>              Labels: external-volumes, mesosphere, myriad
>
> Make it so that either via a slave restart or a out of process "reconfigure" ping, the attributes and resources of a slave can be updated to be a superset of what they used to be.



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