[
https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536280#comment-14536280
]
Cody Maloney commented on MESOS-1739:
-------------------------------------
The biggest thing which came up in my old patchset was race conditions around
re-registering in how the mesos registerSlave / reregisterSlave code is setup
which probably will need some structural reworking.
The case that was broken in my patch set is when a slave tries to register
multiple times because it hasn't gotten a response from the master yet, and 1+
of those retries aren't identical to the first because they contain different
resources / attributes (The slave started re-registration, then was restarted
with new attributes before the master fully processed it), the master doesn't
notice and just discards them as repeats.
> 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
> Assignee: Cody Maloney
> Labels: mesosphere
>
> 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)
