[jira] [Updated] (MESOS-5368) Consider introducing persistent agent ID
[ https://issues.apache.org/jira/browse/MESOS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Harper updated MESOS-5368: -- Affects Version/s: 1.2.1 > 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)
[jira] [Updated] (MESOS-5368) Consider introducing persistent agent ID
[ https://issues.apache.org/jira/browse/MESOS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Harper updated MESOS-5368: -- Affects Version/s: 1.3.0 > 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)
[jira] [Updated] (MESOS-5368) Consider introducing persistent agent ID
[ https://issues.apache.org/jira/browse/MESOS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Dasgupta updated MESOS-5368: - Assignee: (was: Abhishek Dasgupta) > 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 > 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.3.4#6332)
[jira] [Updated] (MESOS-5368) Consider introducing persistent agent ID
[ https://issues.apache.org/jira/browse/MESOS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Conway updated MESOS-5368: --- Description: 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. was: 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. > 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 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.3.4#6332)