[
https://issues.apache.org/jira/browse/MESOS-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886050#comment-16886050
]
Benjamin Bannier edited comment on MESOS-9846 at 7/16/19 11:30 AM:
-------------------------------------------------------------------
[~greggomann], with the way the drain config is presented in master and agent
state endpoints it is currently hard to interpret the meaning of
{{max_grace_period}} as represents a value relative to the time the draining
was starting, however that time is not exposed. WDYT about including the start
time in HTTP responses as well? Specifying a duration as opposed to a deadline
is convenient for users _triggering draining_, but hard to interpret after the
fact. Looking back it might also have made sense to allow users to specify a
relative {{max_grace_period}}, but already translate that to a deadline on the
master before instructing the agent to drain.
was (Author: bbannier):
[~greggomann], with the way the drain config is presented in master and agent
state endpoints it is currently hard to interpret the meaning of
{{max_grace_period}} as represents a value relative to the time the draining
was starting, however that time is not exposed. WDYT about including the start
time in HTTP responses as well? Specifying a duration as opposed to a deadline
is convenient for users _triggering draining_, but hard to interpret after the
fact.
> Update UI for agent draining
> ----------------------------
>
> Key: MESOS-9846
> URL: https://issues.apache.org/jira/browse/MESOS-9846
> Project: Mesos
> Issue Type: Task
> Components: webui
> Reporter: Greg Mann
> Assignee: Benjamin Bannier
> Priority: Major
> Labels: foundations, mesosphere
>
> We should expose the new agent metadata in the web UI:
> * Drain info
> * Deactivation state
> It may also be worth exposing unreachable and gone agents in some way, so
> that agents do not simply disappear from the UI when they transition to
> unreachable and/or gone, during or after maintenance.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
