[
https://issues.apache.org/jira/browse/MESOS-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Conway updated MESOS-7317:
-------------------------------
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.
was:
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 receive an offer for the unused resources on the
agent, which will often result in respawning the killed task on the same agent.
> Add master endpoint to deactivate / activate agent
> --------------------------------------------------
>
> Key: MESOS-7317
> URL: https://issues.apache.org/jira/browse/MESOS-7317
> Project: Mesos
> Issue Type: Improvement
> Components: agent, master
> Reporter: Neil Conway
> Labels: mesosphere
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
