Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
In existing CapacityScheduler, when computing headroom of an application, it will only consider "non-labeled" nodes of this application.
But it is possible the application is asking for labeled resources, so headroom-by-label (like 5G resource available under node-label=red) is required to get better resource allocation and avoid deadlocks such as MAPREDUCE-5928.
This JIRA could involve both API changes (such as adding a label-to-available-resource map in AllocateResponse) and also internal changes in CapacityScheduler.