[TEZ-3950] Preempted task attempts intermittently marked as FAILED instead of KILLED

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.9.2, 0.10.0
• Target Version/s: 0.9.2, 0.10.0
• Assignee: Unassigned
• Reporter: Jonathan Turner Eagles
• Created: 05/Jun/18 17:03
• Updated: 05/Feb/19 15:20

Description

TestMockDAGAppMaster.testInternalPreemption intermittently fails with expected:<KILLED> but was:<FAILED>

Crux of the matter is TaskSchedulerManager sends two events

• TaskScheduler#deallocatedContainer->TaskSchedulerManager#containerBeingReleased->Sends AMContainerStopRequest -> TA_CONTAINER_TERMINATING
• AMContainerEventCompleted -> TA_CONTAINER_TERMINATED_BY_SYSTEM

In order to kill a task attempt correctly the second message loop must complete first. The first path is longer so the second message loop completes almost always first. When the first message loop completes first, then the task attempt is marked as FAILED and not KILLED.

Issue Links

• is related to: TEZ-4036 TestMockDAGAppMaster#testInternalPreemption should assert for failed state