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/11/19 02:06:17 UTC

[jira] [Reopened] (MESOS-243) driver stop() should block until outstanding requests have been persisted

     [ https://issues.apache.org/jira/browse/MESOS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler reopened MESOS-243:
-----------------------------------

      Assignee:     (was: Benjamin Mahler)

Unfortunately it turns out this is not quite enough to eliminate the need for a sleep. This is because the call to Process::send itself is asynchronous and stop() cannot ensure this message has been flushed through libev. This would require some changes to libprocess to ensure we can flush or wait for outstanding requests.

See: https://reviews.apache.org/r/15662/

> 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
>
> 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)