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
[BUG] redis cluster can not failover #13234
Comments
How many other instances of redis are online at the restart of the replica ? Is there enought other instance to acknowledge that it is the master that disappears from cluster ? Because without other instances to agree, the replica can be the one that is partitionned and should not become the master |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
redis version: 6.2.7
redis cluster nodes:9(each have 1 replica)
I stop a primary shard and its corresponding replica shard, and then start the replica shard. After 20 minutes, the replica shard is not promoted to the primary shard.
error message:
To reproduce
After the primary shard and its replica shard are stopped at the same time, only the replica shard is started, and the replica shard will never be automatically promoted to the primary shard.
Expected behavior
The replica shard is automatically promoted to primary.
Additional information
The text was updated successfully, but these errors were encountered: