mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deshi Xiao (JIRA)" <>
Subject [jira] [Commented] (MESOS-5368) Consider introducing persistent agent ID
Date Wed, 30 Nov 2016 22:23:58 GMT


Deshi Xiao commented on MESOS-5368:

Yeah, Yan,

I think Currently persistent agent Id definition is not clarify.  i have
reading the MESOS-5368, MESOS-6223, it let me got lost. MESOS-1739 need
agent id is persistent in slave reconfiguration case. So i add this issue
block on MESOS-5368.

I think MESOS-5368 is a feature. Do you have same result?

I want to resolve it,but i not found the starting point. anyone can guide
me and let me know which way is good start.

Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)

> Consider introducing persistent agent ID
> ----------------------------------------
>                 Key: MESOS-5368
>                 URL:
>             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

View raw message