You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2019/06/29 00:42:00 UTC
[jira] [Commented] (MESOS-9818) Implement minimal agent-side
draining handler
[ https://issues.apache.org/jira/browse/MESOS-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875328#comment-16875328 ]
Greg Mann commented on MESOS-9818:
----------------------------------
{code}
commit b2cfcecb34e76b9a5380bf27f8a2b650510ed158 (HEAD -> master, origin/master, origin/HEAD, merge)
Author: Greg Mann <gr...@mesosphere.io>
Date: Fri Jun 28 13:13:58 2019 -0700
Added agent capability for agent draining.
This patch adds a new required agent capability, AGENT_DRAINING,
which indicates to the master that the agent is capable of
handling automatic task draining via the `DrainSlaveMessage`.
Review: https://reviews.apache.org/r/70839/
{code}
> Implement minimal agent-side draining handler
> ---------------------------------------------
>
> Key: MESOS-9818
> URL: https://issues.apache.org/jira/browse/MESOS-9818
> Project: Mesos
> Issue Type: Task
> Components: agent
> Reporter: Greg Mann
> Assignee: Greg Mann
> Priority: Major
> Labels: foundations, mesosphere
>
> To unblock other work that can be done in parallel, this ticket captures the implementation of a handler for the {{DrainSlaveMessage}} in the agent which will:
> * Checkpoint the {{DrainInfo}}
> * Populate a new data member in the agent with the {{DrainInfo}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)