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

Vladimir Petrovic commented on MESOS-243:
-----------------------------------------

I've just uploaded the updated patch, sorry for the delay. You are right about 
the possibility that the driver might keep on waiting, I will take a look now 
at   MESOS-5262.

> 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
>            Assignee: Vladimir Petrovic
>             Fix For: 1.1.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.3.4#6332)

Reply via email to