supervisor/autoscaler: Skip scaling when partitions are less than minTaskCount #17335
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
When supervisors are configured with incorrect lag based scaling config, where minTaskCount is greater than the partitions on the stream, it always tries to issue scaling actions which are redundant but causes tasks to get published more frequently than needed.
We are handling this situation when maxTaskCount is greater than partitions, this PR uses the same check for minTaskCount too.
Key changed/added classes in this PR
LagBasedAutoScaler
This PR has: