[YARN-1408] Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.5.0
• Component/s: resourcemanager
• Target Version/s: 2.5.0
• Assignee: Sunil G
• Reporter: Sunil G
• Created: 13/Nov/13 06:11
• Updated: 15/Aug/14 05:44
• Resolved: 15/Jul/14 23:47

Description

Capacity preemption is enabled as follows.

• yarn.resourcemanager.scheduler.monitor.enable= true ,
• yarn.resourcemanager.scheduler.monitor.policies=org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.ProportionalCapacityPreemptionPolicy

Queue = a,b
Capacity of Queue A = 80%
Capacity of Queue B = 20%

Step 1: Assign a big jobA on queue a which uses full cluster capacity
Step 2: Submitted a jobB to queue b which would use less than 20% of cluster capacity

JobA task which uses queue b capcity is been preempted and killed.

This caused below problem:
1. New Container has got allocated for jobA in Queue A as per node update from an NM.
2. This container has been preempted immediately as per preemption.

Here ACQUIRED at KILLED Invalid State exception came when the next AM heartbeat reached RM.
ERROR org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: Can't handle this event at current state
org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: ACQUIRED at KILLED

This also caused the Task to go for a timeout for 30minutes as this Container was already killed by preemption.
attempt_1380289782418_0003_m_000000_0 Timed out after 1800 secs

Issue Links

• is blocked by: YARN-2143 Merge common killContainer logic of Fair/Capacity scheduler into AbstractYarnScheduler