[MESOS-5368] Consider introducing persistent agent ID

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.1, 1.3.0
• Labels: mesosphere
• Assignee: Unassigned
• Reporter: Neil Conway
• Created: 12/May/16 10:40
• Updated: 29/Jan/18 23:27

Description

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.

Issue Links

• is related to: MESOS-4894 Volumes, reservations can move to new agent IDs after partition
• is related to: MESOS-7426 Support for agent lifecycle management.
• relates to: MESOS-6223 Allow agents to re-register post a host reboot
• relates to: MESOS-3826 Add an optional unique identifier for resource reservations