[
https://issues.apache.org/jira/browse/MESOS-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258774#comment-14258774
]
Nishant Suneja commented on MESOS-999:
--------------------------------------
Ok. So, if I understand the problem statement correctly, we want to start the
executor registration timeout timer, only after the executor process has forked
of successfully from slave.
So, the plan is to leverage the onReady() callback of the Future instance
associated with the executor process, and start the timer ONLY on receiving
this callback. This should ensure that registration timer starts only after
successful forking.
> Slave should wait() and start executor registration timeout after launch
> -------------------------------------------------------------------------
>
> Key: MESOS-999
> URL: https://issues.apache.org/jira/browse/MESOS-999
> Project: Mesos
> Issue Type: Bug
> Components: isolation
> Affects Versions: 0.18.0
> Reporter: Ian Downes
> Assignee: Nishant Suneja
> Priority: Minor
>
> The current code will start launch a container and wait on it before the
> launch is complete. We should do this only after the container has
> successfully launched. Likewise for the executor registration timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
