You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Lei Xu (JIRA)" <ji...@apache.org> on 2016/07/25 07:13:20 UTC

[jira] [Commented] (MESOS-5368) Consider introducing persistent agent ID

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

Lei Xu commented on MESOS-5368:
-------------------------------

+1

> Consider introducing persistent agent ID
> ----------------------------------------
>
>                 Key: MESOS-5368
>                 URL: https://issues.apache.org/jira/browse/MESOS-5368
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Neil Conway
>            Assignee: Abhishek Dasgupta
>              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 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.3.4#6332)