> On Sept. 15, 2017, 11:36 a.m., Andrei Budnik wrote:
> > src/launcher/default_executor.cpp
> > Line 1379 (original), 1396 (patched)
> > <https://reviews.apache.org/r/62212/diff/2/?file=1820838#file1820838line1406>
> >
> > If a default executor is allowed to call `launchGroup` more than once, then
there may be a case when some containers are launched already, while others not.
I think if this is possible, the error was already in the existing code?
- Benno
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62212/#review185478
-----------------------------------------------------------
On Sept. 13, 2017, 2:52 p.m., Benno Evers wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62212/
> -----------------------------------------------------------
>
> (Updated Sept. 13, 2017, 2:52 p.m.)
>
>
> Review request for mesos, Andrei Budnik and Alexander Rukletsov.
>
>
> Bugs: MESOS-7941
> https://issues.apache.org/jira/browse/MESOS-7941
>
>
> Repository: mesos
>
>
> Description
> -------
>
> This gives schedulers more information about a tasks status,
> in particular it gives a better estimate of a tasks start time
> and helps differentiating between tasks stuck in TASK_STAGING
> and tasks stuck in TASK_STARTING.
>
>
> Diffs
> -----
>
> docs/high-availability-framework-guide.md 73743aba31f9d0ca827d318e2ecb4752a91b1be0
> src/docker/executor.cpp e9949f652cd8527991ebfdfbf14e68b4c958fe79
> src/launcher/default_executor.cpp 106b7f2e0244d211c66b237b5d1c51f43fc6e529
> src/launcher/executor.cpp 951597b576b4912541dd87d52dcb981393e58082
>
>
> Diff: https://reviews.apache.org/r/62212/diff/2/
>
>
> Testing
> -------
>
>
> Thanks,
>
> Benno Evers
>
>
|