You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Marco Massenzio (JIRA)" <ji...@apache.org> on 2015/11/11 00:10:11 UTC

[jira] [Commented] (MESOS-3220) Offer ability to kill tasks from the API

    [ https://issues.apache.org/jira/browse/MESOS-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999552#comment-14999552 ] 

Marco Massenzio commented on MESOS-3220:
----------------------------------------

To revive this thread - a couple of clarifying points:

1. Maintenance
This is meant to augment the Maintenance Primitives (MESOS-1474) and certainly *not* to replace it.
In particular, this endpoint (which ought to be scriptable, for automated maintenance scripts) would enable operators to kill "recalcitrant" frameworks/tasks which, for whatever reason, do not follow the Inverse Offer mechanism;

2. Repairs
There may be situations in which the task itself gets in a funky state and needs to be killed, without Mesos necessarily noticing it (ie, we cannot rely on the {{TASK_LOST}}/{{TASK_KILLED}} conditions).
Once that happens, however, the Framework will be notified (via the usual Mesos mechanisms) and can thus decide whether to re-schedule the task (possibly, somewhere else).

3. Remote termination
Using tools such as the {{DCOS CLI}} we want to enable  users to reach out to Mesos Master directly (possibly bypassing the framework) and terminate a task, without requiring every framework developer to re-implement the same API (so, this would be a "common service" that Mesos offers to framework developers, that they wouldn't have to worry about).

4. Security
There is obviously the expedient (if somewhat draconian) "firewalling" ability, to prevent outright access to this endpoint.
At a finer-grained level, we would consider using ACLs (probably in line with what is currently being done for the Maintenance Primitives) to authorize access to this functionality.

> 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)