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

Yan Xu commented on MESOS-5368:
-------------------------------

[~vinodkone] This sounds good to me, just a few details which I hope are 
covered:

* Right now when the agent recovery fails we recommend {{rm -f 
<work_dir>/meta/slaves/latest}}, I guess going forward this will be changed to 
{{rm -f <work_dir>}}?
* Currently the agent would GC (instead of deleting immediately) all sandbox 
data from previous agents under the same <work_dir>. Going forward are we 
requiring that "in order to start with a new agent, all sandboxes need to be 
deleted immediately (because of {{rm -f <work_dir>}})"?
* Currently if we delete work_dir, the data in external volumes remain 
unchanged and will reappear when these volumes are used later. Should we 
provide a "purging" functionality to clean them up?
* Should we eventually remove the "slaves" and "latest" file system structure 
since there is only going to be one agent per work dir?

> 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