Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
After YUNIKORN-807, node sorting uses a scoring algorithm which uses the largest resource share to determine priority. However, resource units are not taken into account, and consequently, either fair or binpacking tends to look almost exclusively at the largest absolute values for units. In some environments this can lead to priority inversions.
We should instead calculate in-use percentages for each resource, and then weight them to arrive at an overall usage percentage, which can then be used for scoring. Weights can be controlled at the partition level.
Configuration is as follows:
partitions: - name: default nodesortpolicy: type: fair resourceweights: vcore: 4.0 memory: 1.0 queues: - name: root submitacl: '*'
In this example, vcore is weighted double what memory is. If resourceweights is not specified, the configuration is equivalent to:
{ vcore: 1, memory: 1}
For example, in the default configuration, if a node has 60% of its vcores in use, and 20% of its memory in use, node usage would be calculated at 40% using equal weights. In the example given above, usage would be calculated as 52%.
Attachments
Issue Links
- is required by
-
YUNIKORN-852 Document changes from YUNIKORN-847
- Closed
- relates to
-
YUNIKORN-807 Improve performance of node sorting
- Closed
- supercedes
-
YUNIKORN-831 node sorting should check other resources of nodes instead of comparing node id directly
- Closed
-
YUNIKORN-21 Optimize node sorting algorithms
- Closed
- links to