[
https://issues.apache.org/jira/browse/MESOS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700924#comment-15700924
]
Yan Xu commented on MESOS-5368:
-------------------------------
Revising my earlier comment a bit:
Currently the master in a number of occasions sends {{ShutdownMessage}} to the
agent or the agent shuts down itself. These shutdowns invalidate the current
agent ID and they are all due to some erroneous conditions or explicit operator
intervention so the action to abandon the current agent state (i.e., the state
under {{<work_dir>/meta/slaves/latest}} is justified.
The argument in MESOS-6223 is that rebooting a host doesn't necessarily suggest
any "error" and the agent ID could be reused unless some separate errors occur.
Therefore the concept of a persistent agent ID (which binds to the work_dir) is
still valuable even after MESOS-6223 is fixed.
> Consider introducing persistent agent ID
> ----------------------------------------
>
> Key: MESOS-5368
> URL: https://issues.apache.org/jira/browse/MESOS-5368
> Project: Mesos
> Issue Type: Improvement
> Reporter: Neil Conway
> Labels: mesosphere
>
> Currently, agent IDs identify a single "session" by an agent: that is, an
> agent receives an agent ID when it registers with the master; it reuses that
> agent ID if it disconnects and successfully reregisters; if the agent shuts
> down and restarts, it registers anew and receives a new agent ID.
> It would be convenient to have a "persistent agent ID" that remains the same
> for the duration of a given agent {{work_dir}}. This would mean that a given
> persistent volume would not migrate between different persistent agent IDs
> over time, for example (see MESOS-4894). If we supported permanently removing
> an agent from the cluster (i.e., the {{work_dir}} and any volumes used by the
> agent will never be reused), we could use the persistent agent ID to report
> which agent has been removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
