Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
For each partitioned request on partitioned node, we are checking it twice. one on exclusive_scheduling, the other on non_exclusive_scheduling; Probably we need a higher level mapping for resource requests: (partition -> all requests) to avoid double checking for partitioned requests on partitioned node.
Attachments
Issue Links
- relates to
-
YARN-3361 CapacityScheduler side changes to support non-exclusive node labels
- Resolved