Fix the logic to calculate minResources #543
Merged
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.
I fixed the logic to calculate minResources so that
calculatePGMinResource
treats the launcher as a replica of higher priority when we don't set priorityClasses.I faced the issue at #540 (comment).
Background:
In the current implementation, if the launcher and workers have the same priority,
calculatePGMinResource
randomly selects prioritized replicas. This means the launcher might be treated as a lower priority than the worker replica when we don't set priorityClass in both replicas.