[YARN-3026] Move application-specific container allocation logic from LeafQueue to FiCaSchedulerApp

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: capacityscheduler
• Hadoop Flags: Reviewed
• Assignee: Wangda Tan
• Reporter: Wangda Tan
• Created: 09/Jan/15 21:38
• Updated: 30/Aug/16 01:28
• Resolved: 24/Jul/15 21:03

Description

Have a discussion with Vinod Kumar Vavilapalli and Jian He:

In existing Capacity Scheduler, all allocation logics of and under LeafQueue are located in LeafQueue.java in implementation. To make a cleaner scope of LeafQueue, we'd better move some of them to FiCaSchedulerApp.

Ideal scope of LeafQueue should be: when a LeafQueue receives some resources from ParentQueue (like 15% of cluster resource), and it distributes resources to children apps, and it should be agnostic to internal logic of children apps (like delayed-scheduling, etc.). IAW, LeafQueue shouldn't decide how application allocating container from given resources.

Issue Links

• is depended upon by: YARN-1651 CapacityScheduler side changes to support increase/decrease container resource.