-
Notifications
You must be signed in to change notification settings - Fork 23.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support auto-rebalance feature in Redis Cluster #2206
Comments
Hello, Automatic-rebalance is planned for iteration 2 of Redis Cluster, however manual rebalance already works but is fully manual, that is, you need to tell Redis Cluster from which node to what other node to move how many hash slots. The idea for the future is:
We need to see Redis Cluster v1 more deployed / used / battle tested in order to start new developments, for now the focus is into supporting what we got so far. Thanks for your feedback! Closing since this is one of the fundamental feature planned for Redis developments, so for sure we'll not forget :-) |
OK, thank you! |
Thank you, Salvatore. Please consider a two-phase process here? |
Note for the future: When a new master is added to the cluster, it should not auto-rebalance until at least one slave is assigned to it. Otherwise there could be a failure in the migration and K-V could be lost. |
Is the auto balancing feature available now? |
Can anyone please clarify if the auto-rebalancing feature available now? |
Is this feature available? |
Currently, Redis Cluster can implements auto-failover which helps us a lot. i think it can also provide such a feature : auto-rebalance according to the percentage of memory-used / maxmemory and several other factors like cpu when we encounter follower scenarios:
Although we can make it resort to client api, but if the Cluster can provide an option to make it Automatic or manual , that will be better.
Anyway, As a user, maybe we should implement it on our own according to our specific scenario.
The text was updated successfully, but these errors were encountered: