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 Mon, 29 Jan 2018 23:28:00 GMT


Yan Xu commented on MESOS-5368:

[~vinodkone] It still seems to me that the proposal to tie the current agent ID (and the
latest agent symlink) to the entire work_dir is problematic. Even with MESOS-1739 there still
exits possibilities for the agent's checkpointed info to lose compatibility with the new
configuration. If that happens {{rm -f <meta>/slaves/latest}} is still the cleaned way
to discard the state of the "agent" (and not the resources it manages). So we can still end
up with the need to clean up the "agent" but keep the metadata for the resources on the host.
Of course we should design this in light of the local resource providers.

> 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
>            Priority: Major
>              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