[YARN-3361] CapacityScheduler side changes to support non-exclusive node labels

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: capacityscheduler
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: Wangda Tan
• Reporter: Wangda Tan
• Created: 17/Mar/15 21:06
• Updated: 05/Jun/19 20:35
• Resolved: 14/Apr/15 18:47

Description

According to design doc attached in YARN-3214, we need implement following logic in CapacityScheduler:
1) When allocate a resource request with no node-label specified, it should get preferentially allocated to node without labels.

2) When there're some available resource in a node with label, they can be used by applications with following order:

• Applications under queues which can access the label and ask for same labeled resource.
• Applications under queues which can access the label and ask for non-labeled resource.
• Applications under queues cannot access the label and ask for non-labeled resource.

3) Expose necessary information that can be used by preemption policy to make preemption decisions.

Issue Links

• is duplicated by: YARN-3213 Respect labels in Capacity Scheduler when computing user-limit
• is duplicated by: YARN-4839 ResourceManager deadlock between RMAppAttemptImpl and SchedulerApplicationAttempt
• is duplicated by: YARN-2176 CapacityScheduler loops over all running applications rather than actively requesting apps
• is related to: YARN-3486 Duplicate check for partitioned request on partitioned node