[ 
https://issues.apache.org/jira/browse/MESOS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199495#comment-16199495
 ] 

Vinod Kone commented on MESOS-5368:
-----------------------------------

[~xujyan] As part of MESOS-7426, we decided that agent id is what is tied to 
the "work_dir". When an agent is marked gone, we are marking the agent id as 
gone. This means that frameworks getting the agent gone signal can assume that 
everything (tasks, reservations, volumes) on that agent is gone. While it is 
technically possible for an operator to manually go and fiddle with the on-disk 
state so that agent can have a new id but still keep old reservations/volumes, 
that is just an implementation limitation. We might elect to disallow that in 
the future. 

Once we allow agent re-configuration in MESOS-1739, the idea is that the agent 
can keep its agent id and still update its info (resources, attributes, domains 
etc) and signal the frameworks about the update.

Hope that makes sense.

> Consider introducing persistent agent ID
> ----------------------------------------
>
>                 Key: MESOS-5368
>                 URL: https://issues.apache.org/jira/browse/MESOS-5368
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 1.2.1, 1.3.0
>            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.4.14#64029)

Reply via email to