[YARN-9730] Support forcing configured partitions to be exclusive based on app node label

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.10.0, 3.3.0, 3.2.2, 3.1.4
• Labels: release-blocker
• Target Version/s: 2.10.0
• Assignee: Jonathan Hung
• Reporter: Jonathan Hung
• Created: 08/Aug/19 22:29
• Updated: 26/Sep/19 06:29
• Resolved: 26/Sep/19 00:56

Description

Use case: queue X has all of its workload in non-default (exclusive) partition P (by setting app submission context's node label set to P). Node in partition Q != P heartbeats to RM. Capacity scheduler loops through every application in X, and every scheduler key in this application, and fails to allocate each time since the app's requested label and the node's label don't match. This causes huge performance degradation when number of apps in X is large.

To fix the issue, allow RM to configure partitions as "forced-exclusive". If partition P is "forced-exclusive", then:

• 1a. If app sets its submission context's node label to P, all its resource requests will be overridden to P
• 1b. If app sets its submission context's node label Q, any of its resource requests whose labels are P will be overridden to Q
• 2. In the scheduler, we add apps with node label expression P to a separate data structure. When a node in partition P heartbeats to scheduler, we only try to schedule apps in this data structure. When a node in partition Q heartbeats to scheduler, we schedule the rest of the apps as normal.

Issue Links

• is related to: YARN-9858 Optimize RMContext getExclusiveEnforcedPartitions