[
https://issues.apache.org/jira/browse/MESOS-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037416#comment-15037416
]
Guangya Liu commented on MESOS-3892:
------------------------------------
I know that we already have lot of discussions to talk whether the master can
kill task or not. For some frameworks, it may not implement the
{{termiateTask()}} so that once the executor was killed, the task will become
TASK_FAILED and all resources will be recovered but task continues running,
this will cause the host over committed, kubernetes on mesos is such a case, I
filed a ticket here to trace the k8s on mesos issue:
https://github.com/kubernetes/kubernetes/issues/18066
Killing task directly by master may not able to make sure QoS but it can make
sure the resources usage is correct in case some executors do not implement
{{terminateTask()}} API. Is it possible to add a new field in Framework to
control kill task or executor when the tasks on this framework is being
preempted.
> Add a helper function to the Agent to retrieve the list of executors that are
> using optimistically offered, revocable resources.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-3892
> URL: https://issues.apache.org/jira/browse/MESOS-3892
> Project: Mesos
> Issue Type: Bug
> Reporter: Artem Harutyunyan
> Assignee: Klaus Ma
> Labels: mesosphere
>
> {noformat}
> class Slave {
> ...
> // How the master currently keeps track of executors.
> hashmap<FrameworkID, hashmap<ExecutorID, ExecutorInfo>> executors;
> ...
> // Returns the list of executors that are using optimistically-
> // offered, revocable resources.
> list<ExecutorID> getEvictableExecutors() { ... }
> ...
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
