mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <>
Subject [jira] [Commented] (MESOS-5368) Consider introducing persistent agent ID
Date Thu, 27 Jul 2017 05:58:03 GMT


Yan Xu commented on MESOS-5368:

This ticket is not a duplicate of MESOS-6223. With MESOS-6223 the agent ID doesn't automatically
change after a host reboot but it still can, due to agent info mismatch (e.g., {{--resources}}
and {{--attributes}}).

I think there is still need for an ID that "remains the same for the duration of a given agent
work_dir", even the initial design doc of MESOS-7426 doesn't capture this.

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

View raw message