[
https://issues.apache.org/jira/browse/MESOS-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552139#comment-14552139
]
Itamar Ostricher commented on MESOS-2751:
-----------------------------------------
In the example I described on the mailing list, it looks like the
UnregisterFrameworkMessage was never sent without sleeping. As can be seen in
the screenshot on the mailing list, the previous framework remains "active"...
> Stopping the scheduler driver w/o failover requires a sleep to ensure the
> UnregisterFrameworkMessage is delivered.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-2751
> URL: https://issues.apache.org/jira/browse/MESOS-2751
> Project: Mesos
> Issue Type: Bug
> Components: framework
> Reporter: Benjamin Mahler
> Priority: Minor
>
> When the call to {{driver.stop(false)}} completes, the
> UnregisterFrameworkMessage will be sent asynchronously once the
> SchedulerProcess processes the dispatch event.
> This requires schedulers to sleep to ensure the message is processed:
> http://markmail.org/thread/yuzq5i3hkpttxc2s
> We could block on a Future result from the dispatch, if safe. But this still
> doesn't ensure the message is flushed out of libprocess. And without
> acknowledgements, we don't know if the master has successfully unregistered
> the framework.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
