[
https://issues.apache.org/jira/browse/MESOS-9556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761918#comment-16761918
]
Greg Mann commented on MESOS-9556:
----------------------------------
Perhaps a new state like {{SLAVE_DOWN}} or {{SLAVE_DRAINED}} might make sense?
This would represent the case where an agent has been removed but may come back
after a time.
> Define agent states for cases handled by 'Master::_removeSlave()'
> -----------------------------------------------------------------
>
> Key: MESOS-9556
> URL: https://issues.apache.org/jira/browse/MESOS-9556
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Greg Mann
> Priority: Major
> Labels: agent-lifecycle, foundations, mesosphere
>
> The {{Master::_removeSlave()}} function currently handles three cases of
> agent removal:
> * Starting maintenance on an agent via the 'startMaintenance()' handler
> * When an agent submits a new registration from a previously-known IP:port,
> via the _registerSlave() method
> * When an agent shuts itself down via an UnregisterSlaveMessage
> In these cases, the agent is not transitioned to a new state in the master,
> it is simply removed. We should define agent states for these cases and
> ensure that the master stores these agent IDs and/or agent infos.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
