[YARN-201] CapacityScheduler can take a very long time to schedule containers if requests are off cluster

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.3, 2.0.1-alpha
• Fix Version/s: 2.0.3-alpha, 0.23.5
• Component/s: capacityscheduler
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 05/Nov/12 15:47
• Updated: 06/Feb/13 17:05
• Resolved: 07/Nov/12 21:58

Description

When a user runs a job where one of the input files is a large file on another cluster, the job can create many splits on nodes which are unreachable for computation from the current cluster. The off-switch delay logic in LeafQueue can cause the ResourceManager to allocate containers for the job very slowly. In one case the job was only getting one container every 23 seconds, and the queue had plenty of spare capacity.