Launch fast scaling/upgrading when having primary-replicas and purgeKeysOnRebalance is active#46
Merged
albertompe merged 1 commit intomainfrom Feb 27, 2026
Merged
Conversation
samuelli00
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Scaling and upgrading operations are executed in slow way for primary-replicas Redkey clusters, even if the parameter
purgeKeysOnRebalanceis set to true. This leads to operations taking too long.When
purgeKeysOnRebalanceis active, losing the keys isn't a concern; we prioritize speed in operations. Therefore, in these cases, operations should be launched in fast mode.The check that determines whether to launch the scaling or upgrade in fast mode has been modified according to this premise.