[MESOS-9052] Default executor should commit suicide if it cannot receive HTTP responses for LAUNCH_NESTED_CONTAINER calls.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.0, 1.5.0, 1.6.0, 1.7.0
• Component/s: executor
• Epic Link: Default Executor improvements
• Sprint: Mesosphere Sprint 2018-27
• Story Points: 3
• Assignee: Gastón Kleiman
• Reporter: Chun-Hung Hsiao
• Shepherd: Qian Zhang
• Created: 05/Jul/18 18:05
• Updated: 13/Sep/18 21:44

Description

If there is a network problem (e.g., a routing problem), it is possible that the agent has received LAUNCH_NESTED_CONTAINER calls from the default executor and launched the nested container, but the executor does not get the HTTP response. This would result in tasks stuck at TASK_STARTING forever. We should consider making the default executor commit suicide if it does not receive the response in a reasonable amount of time.