[
https://issues.apache.org/jira/browse/MESOS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824167#comment-13824167
]
Benjamin Mahler commented on MESOS-243:
---------------------------------------
I've got a patch to make {{join()}} block on outstanding requests (if one calls
{{stop()}} it will still return immediately, but {{join()}} will wait for the
outstanding requests as intended). That is, in your main function if you're
calling {{driver.run()}}, it will wait for the outstanding requests after
you've called {{stop()}}.
Here's the review: https://reviews.apache.org/r/15597/
> driver stop() should block until outstanding requests have been persisted
> -------------------------------------------------------------------------
>
> Key: MESOS-243
> URL: https://issues.apache.org/jira/browse/MESOS-243
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0, 0.15.0,
> 0.14.1, 0.14.2
> Reporter: brian wickman
> Fix For: 0.16.0
>
>
> in our executor, we send a terminal status update message and immediately
> call driver.stop(). it turns out that the status update is dispatched
> asynchronously and races with driver shutdown, causing tasks to instead
> periodically go into LOST state.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
