[
https://issues.apache.org/jira/browse/MESOS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-97:
---------------------------------
Description: Currently once a master determines that a slave is "removed"
it will not allow it to reregister ... this could cause an entire cluster to be
without slaves. The current solution has always just been to roll the master. A
better solution is to allow a slave to reregister even if it has been removed.
(was: Currently once a master determines that a slave is "deactivated" it will
not allow it to reregister ... this could cause an entire cluster to be without
slaves. The current solution has always just been to roll the master. A better
solution is to allow a slave to reregister even if it has been deactivated.)
Summary: Allow a slave to reregister even if it has been removed.
(was: Allow a slave to reregister even if it has been deactivated.)
(Updated terminology s/deactivated/removed)
> Allow a slave to reregister even if it has been removed.
> --------------------------------------------------------
>
> Key: MESOS-97
> URL: https://issues.apache.org/jira/browse/MESOS-97
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Hindman
> Assignee: Benjamin Hindman
> Labels: twitter
>
> Currently once a master determines that a slave is "removed" it will not
> allow it to reregister ... this could cause an entire cluster to be without
> slaves. The current solution has always just been to roll the master. A
> better solution is to allow a slave to reregister even if it has been removed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
