[MESOS-7317] Add master endpoint to deactivate / activate agent

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: agent, master
• Labels: mesosphere
• Epic Link: maintenance-improvements
• Assignee: Unassigned
• Reporter: Neil Conway
• Created: 27/Mar/17 23:03
• Updated: 07/Aug/18 18:58

Description

This would allow the operator to deactivate and then subsequently activate an agent. The allocator does not make offers for deactivated agents; this functionality would be useful to help operators "manually (incrementally) drain" the tasks running on an agent, e.g., before taking the agent down.

At present, if the operator causes a framework to kill a task running on the agent, the framework will often receive an offer for the unused resources on the agent, which will often result in respawning the killed task on the same agent.

Issue Links

• duplicates: MESOS-1476 Provide endpoints for deactivating / activating slaves.
• is related to: MESOS-6058 Register slave in deactivate mode
• is related to: MESOS-6828 Consider ways for frameworks to ignore offers with an Unavailability
• is related to: MESOS-7155 Mesos Maintenance Primitives ("Drain Mode" could not see it working)
• relates to: MESOS-7201 Maintenance primitive Improvements