[
https://issues.apache.org/jira/browse/MESOS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129014#comment-14129014
]
Yan Xu commented on MESOS-243:
------------------------------
Making messages are flushed still aren't sufficient to ensure it's received. We
can have ExecutorDriver.join() wait for all status updates to be acked.
> 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.14.1,
> 0.14.2, 0.15.0
> Reporter: brian wickman
>
> 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.3.4#6332)
