[
https://issues.apache.org/jira/browse/MESOS-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626768#comment-14626768
]
Timothy Chen commented on MESOS-999:
------------------------------------
I agree the launch timeout isn't a solution to the launch timeout, but as we
include more phases into the containerizer now it does becomes a bit too coarse
to have only one end to end timeout to for the whole chain, as users might have
different tolerance of the different steps it take.
I think this is more about the flexibility for the users to say I know my
images is going to be huge so I want to be able to allow a large timeout for
the image provisioining or prepraition phase, but not really want to wait too
long for the registration as that's not expected.
What solutions do you have in mind that you think can get away from having a
more finer timeout?
> 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
> 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)
