[YARN-2456] Possible livelock in CapacityScheduler when RM is recovering apps

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: resourcemanager
• Assignee: Jian He
• Reporter: Jian He
• Created: 26/Aug/14 20:15
• Updated: 01/Dec/14 03:11
• Resolved: 12/Sep/14 22:25

Description

Consider this scenario:
1. RM is configured with a single queue and only one application can be active at a time.
2. Submit App1 which uses up the queue's whole capacity
3. Submit App2 which remains pending.
4. Restart RM.
5. App2 is recovered before App1, so App2 is added to the activeApplications list. Now App1 remains pending (because of max-active-app limit)
6. All containers of App1 are now recovered when NM registers, and use up the whole queue capacity again.
7. Since the queue is full, App2 cannot proceed to allocate AM container.
8. In the meanwhile, App1 cannot proceed to become active because of the max-active-app limit