[
https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214659#comment-15214659
]
Adam B commented on MESOS-1739:
-------------------------------
But even changing attributes to a superset (or changing existing values) could
require killing tasks, depending on the framework. Imagine your framework is
running sensitive tasks on a node, and then the operator tags the node with the
"public_internet_access=true" attribute, because the node is now in the open.
You would want to be alerted so you could kill/move your sensitive tasks, even
though it's a new attribute.
For resources, adding new resources would not require frameworks to be notified
(beyond the existing offer mechanism) nor require tasks to be killed, because
existing tasks are not consuming those resources. Removing resources could
require killing tasks, if there are not enough resources left after the change
to keep running all tasks. Or the agent might just prevent the operator from
reducing resources below current consumption.
Adding/changing/removing attributes, however, requires frameworks to be
notified.
> 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)
