YARN-11828. Non-exclusive resource allocation respect queue's max capacity #7753
+110
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
Now when doing non-exclusive resource allocation, queue's max capacity on the partition will be considered to be 100%. In an ideal situation, preemption policy will reclaim resource back when partitoned-resource-request comes back.
But our cluster has not enabled preemption, so a queue may use all resource on the partition and block the partitoned-resource-request of other queues.
In this situation, we hope queue's max capacity will be respect when doing non-exclusive resource allocation.
How was this patch tested?
unit test