[
https://issues.apache.org/jira/browse/MESOS-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731323#comment-14731323
]
Marco Massenzio commented on MESOS-3220:
----------------------------------------
{quote}
Framework knowing about it after the task gets killed is likely not enough.
Frameworks typically plan redundancy of tasks (e.g., replicas) based on
"unplanned" random failures in a DC. Adding these sort of endpoints violates
such assumptions.
{quote}
Right - the assumption here is that the {{kill}} command is issued against
misbehaving/rogue frameworks/tasks that do no offer that option (or maybe, they
do, but they are not reachable from the subnet(s) where the user's machine is
sitting).
So, this would be some sort of "emergency brake" for unplanned
outages/emergency actions.
{quote}
For example, for planned machine maintenance ...
Should we do something similar for this endpoint?
{quote}
The main difference is (I believe) that in this case there is no "planning
window" and/or the user cannot (or will not) wait for the task / framework to
complete and go away by its own volition - or it could entirely ignore the
(polite) requests from Master to relinquish resources.
{quote}
Also, I don't follow the "disparate ways to talk to every framework" point.
Does DCOS CLI allow launching framework's tasks? If yes, it already knows how
to communicate with frameworks. If not, why should it allow killing them?
Moreover, I am surprised that there are Mesos frameworks out there that have
APIs for launching tasks but not killing them!?
{quote}
Indeed, but that means we would have to re-implement the functionality *every
time* a new framework is added (not to mention, multiple times very similar
code, every time with the odd twists that the single f/w comes up with). It
makes the code bloated and unmaintainable (not to mention, brittle).
This way, we implement it once, we leverage Mesos' awesomeness and everyone is
happy :)
{quote}
I'm asking these hard questions, because...
{quote}
and so you should! thanks for doing so, totally appreciate that this ticket's
description could have done with a better description of the requirements and
maybe a few use cases - maybe we'll add them too.
And if there is some commonality that we can exploit with Aurora's
requirements, even better!
> Offer ability to kill tasks from the API
> ----------------------------------------
>
> Key: MESOS-3220
> URL: https://issues.apache.org/jira/browse/MESOS-3220
> Project: Mesos
> Issue Type: Improvement
> Components: python api
> Reporter: Sunil Shah
> Assignee: Marco Massenzio
> Priority: Blocker
> Labels: mesosphere
>
> We are investigating adding a `dcos task kill` command to our DCOS (and
> Mesos) command line interface. Currently the ability to kill tasks is only
> offered via the scheduler API so it would be useful to have some ability to
> kill tasks directly.
> This is a blocker for the DCOS CLI!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
