[MESOS-8530] Default executor tasks can get stuck in KILLING state

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.2.3, 1.3.1, 1.4.1, 1.5.0
• Fix Version/s: 1.6.0
• Component/s: executor
• Labels: default-executor mesosphere
• Epic Link: Default Executor improvements
• Sprint: Mesosphere Sprint 74, Mesosphere Sprint 75, Mesosphere Sprint 76
• Story Points: 5
• Assignee: Gastón Kleiman
• Reporter: Gastón Kleiman
• Shepherd: Alex R
• Created: 01/Feb/18 21:43
• Updated: 27/Mar/18 09:43
• Resolved: 27/Mar/18 09:43

Description

The default executor will transition a task to TASK_KILLING and mark its container as being killed before issuing the KILL_NESTED_CONTAINER call.

If the kill call fails, the task will get stuck in TASK_KILLING, and the executor won't allow retrying the kill.