You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2016/07/15 09:28:20 UTC

[jira] [Commented] (MESOS-4919) Facilitate custom task and executor finalization.

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

Alexander Rukletsov commented on MESOS-4919:
--------------------------------------------

Good question. Custom executors can interpret kill policy as they want. So I assume your question is related to Mesos-provided executors: command executor and docker executor. Both executors are general purpose, so they don't actually know how to communicate with the underlying task and hence won't be able to deduce the timeout on the fly. Does it make sense?

> Facilitate custom task and executor finalization.
> -------------------------------------------------
>
>                 Key: MESOS-4919
>                 URL: https://issues.apache.org/jira/browse/MESOS-4919
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Alexander Rukletsov
>            Assignee: Alexander Rukletsov
>              Labels: mesosphere
>
> We would like to give frameworks flexibility around how to clean up tasks and executors. This ranges from propagating related timeouts to specifying custom kill policies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)