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

Tim Harper edited comment on MESOS-5368 at 7/26/17 5:52 PM:
------------------------------------------------------------

One particular pain of not having this feature is it takes Mesos longer than 
necessary to recognize that a task is definitely gone. Were we to have 
persistent agent IDs, then, when the agent re-registered, it could tell Mesos, 
"yes, that task is definitely dead", where-as right now it is left in the 
unreachable state until Mesos gives up on the agent.


was (Author: timcharper):
One particular pain of not having this feature is it takes Mesos longer than 
necessary to recognize that a task is definitely gone. Were we to have 
persistent agent IDs, then, when the agent re-registered, it could tell Mesos, 
"yes, that task is definitely dead", where-as right now it is left perpetually 
in the unreachable state until Mesos gives up on the agent.

> 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