You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/12/03 21:15:36 UTC
[jira] [Assigned] (MESOS-768) Executor driver stop() should
dispatch stop to executor process instead of terminating it
[ https://issues.apache.org/jira/browse/MESOS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler reassigned MESOS-768:
-------------------------------------
Assignee: Benjamin Mahler (was: Vinod Kone)
This was fixed here:
{noformat}
commit dd89ea359ec55fbc90b5718d9cdbf021f189c2fa
Author: Benjamin Mahler <bm...@twitter.com>
Date: Fri Nov 15 14:02:58 2013 -0800
Fixed MESOS-243: Made ExecutorDriver.join() wait for outstanding requests.
Review: https://reviews.apache.org/r/15597
{noformat}
> Executor driver stop() should dispatch stop to executor process instead of terminating it
> -----------------------------------------------------------------------------------------
>
> Key: MESOS-768
> URL: https://issues.apache.org/jira/browse/MESOS-768
> Project: Mesos
> Issue Type: Improvement
> Reporter: Vinod Kone
> Assignee: Benjamin Mahler
> Labels: twitter
> Fix For: 0.16.0
>
>
> Similar to what we do in scheduler driver, a stop on executor driver should dispatch the stop to executor processes instead of terminating it. There are couple of advantages with this:
> --> Executor writers don't have to wait an arbitrary amount of time between driver->stop and exiting to ensure any final updates went through.
> --> Will speed up our tests using command executor because it does a sleep 1 sec due to the same reason as above.
--
This message was sent by Atlassian JIRA
(v6.1#6144)