[
https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217617#comment-15217617
]
Deshi Xiao commented on MESOS-1739:
-----------------------------------
in [Design Doc: Updating
SlaveInfo|https://docs.google.com/document/d/1PWv7YIdV3nN2l1oUW7Nybm4KdnxZ7Px2JGc5UM-PKoQ/edit#]
it statement
{quote}
Currently this can only be handled by stopping / draining a mesos slave
entirely (Killing all of its running jobs), removing it from the cluster, then
bringing it back up as a brand new slave.
{quote}
but in my testing it is not true. https://reviews.apache.org/r/45474/
> 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)
