You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@mesos.apache.org by Zhitao Li <zh...@gmail.com> on 2018/05/01 16:42:42 UTC
Re: Review Request 66291: Added support to `max_completion_time` in
default executor.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/66291/
-----------------------------------------------------------
(Updated May 1, 2018, 9:42 a.m.)
Review request for mesos, Jason Lai and James Peach.
Changes
-------
Review comments.
Bugs: MESOS-8725
https://issues.apache.org/jira/browse/MESOS-8725
Repository: mesos
Description
-------
When a task group has multiple tasks:
- each task can have its own `max_completion_time`, or not have one;
- if a task succeeds before its `max_completion_time`, all other tasks
will keep running;
- if a task fails, all other tasks in the same group will fail (as
before);
- if a task does not succeed before its `max_completion_time`, it will
fail with `TASK_FAILED` and reason `REASON_MAX_COMPLETION_TIME_REACHED`,
while other tasks will be killed without above reason.
Diffs (updated)
-----
src/launcher/default_executor.cpp ea0d425bb60e970f209f411632e1d486c279259b
Diff: https://reviews.apache.org/r/66291/diff/4/
Changes: https://reviews.apache.org/r/66291/diff/3-4/
Testing
-------
Thanks,
Zhitao Li