Details
-
Story
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
-
Twitter Mesos Q4 Sprint 3
-
8
Description
We now have a message string inside TaskStatus that provides human readable information about TASK_FAILED.
It would be good to add some structure to the failure reasons, for framework schedulers to act on programmatically.
E.g.
enum TaskFailure {
EXECUTOR_OOM;
EXECUTOR_OUT_OF_DISK;
EXECUTOR_TERMINATED;
SLAVE_LOST;
etc..
}
Attachments
Issue Links
- is related to
-
MESOS-1143 Add a TASK_ERROR task status.
- Resolved
- relates to
-
MESOS-1830 Expose master stats differentiating between master-generated and slave-generated LOST tasks
- Resolved
-
MESOS-1930 Expose TASK_KILLED reason.
- Accepted
-
MESOS-2035 Add reason to containerizer proto Termination
- Resolved
-
MESOS-2522 Add reason field for framework errors
- Resolved