You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2019/06/04 21:45:00 UTC
[jira] [Created] (MESOS-9814) Implement DrainAgent master/operator
call with associated registry actions
Joseph Wu created MESOS-9814:
--------------------------------
Summary: Implement DrainAgent master/operator call with associated registry actions
Key: MESOS-9814
URL: https://issues.apache.org/jira/browse/MESOS-9814
Project: Mesos
Issue Type: Task
Components: master
Reporter: Joseph Wu
We want to add several calls associated with agent draining:
{code}
message Call {
enum Type {
. . .
DRAIN_AGENT = 37;
DEACTIVATE_AGENT = 38;
REACTIVATE_AGENT = 39;
}
. . .
message DrainAgents {
message DrainConfig {
required AgentID agent = 1;
// The duration after which the agent should complete draining.
// If tasks are still running after this time, they will
// be forcefully terminated.
optional Duration max_grace_period = 2;
// Whether or not this agent will be removed permanently
// from the cluster when draining is complete.
optional bool destructive = 3 [default = false];
}
repeated DrainConfig drain_config = 1;
}
message DeactivateAgents {
repeated AgentID agents = 1;
}
message ReactivateAgents {
repeated AgentID agents = 1;
}
}
{code}
Each field will be persisted in the registry:
{code}
message Registry {
. . .
message Slave {
. . .
optional DrainInfo drain_info = 2;
}
. . .
message UnreachableSlave {
. . .
optional DrainInfo drain_info = 3;
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)