Details
Description
During task validation we drop tasks that have errors and send TASK_LOST status updates. In most circumstances a framework will want to relaunch a task that has gone lost, and in the event the task is actually malformed (thus invalid) this will result in an infinite loop of sending a task and having it go lost.
Attachments
Attachments
Issue Links
- relates to
-
MESOS-1736 Completed tasks shown as running
- Resolved
-
MESOS-343 Expose TASK_FAILED reason to Frameworks.
- Resolved
-
MESOS-1830 Expose master stats differentiating between master-generated and slave-generated LOST tasks
- Resolved
-
MESOS-1930 Expose TASK_KILLED reason.
- Accepted
-
AURORA-1141 Handle new TaskState.TASK_ERROR
- Resolved