[
https://issues.apache.org/jira/browse/MESOS-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606268#comment-15606268
]
Cody Maloney commented on MESOS-6078:
-------------------------------------
{{/machine/down}} is very complicated to use for this use case (Requires
posting multiple JSON blobs, which have to follow a format including timestamps
in milliseconds, which have to have multiple fields which match exactly how a
particular mesos agent was launched).
It takes a _lot_ of code and debugging to use and manage it for what is a
simple common task. Also, once there are existing schedules things get more
complicated (And if you want the agent to re-register later....)
> Add a agent teardown endpoint
> -----------------------------
>
> Key: MESOS-6078
> URL: https://issues.apache.org/jira/browse/MESOS-6078
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Affects Versions: 1.0.0, 1.0.1
> Reporter: Cody Maloney
> Assignee: Michael Park
> Labels: mesosphere
>
> Currently, when a whole agent machine is unexpectedly terminated for good
> (AWS terminated the instance without warning), it goes through the mesos
> slave removal rate limit before it's gone.
> If a couple agents / a whole rack goes in a cluster of thousands of agents,
> this can get to be a problem.
> If the agent can be shutdown "cleanly" everything would get scheduled, but
> once the agent is gone, there currently is no good way for an adminitstrator
> to indicate the node is gone / gone and it's tasks are lost / should be
> rescheduled if appropriate as soon as possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
