[QUESTION]What are the side affects of setting cluster-allow-replica-migration to "no"?

[anu25052608]

We are using Redis cluster where we manage redis cluster via an operator. The operator takes care of making sure enouhg configured primaries are there in the system, it assigns cluster slots to these primaries initially, identifies suitable k8s redis pods which can be replica to each primary and so forth.

We recently encountered an issue during Rolling upgrade of these pods, where one of the replica which was supposed to failover, instead decided to move to an orphaned master as per below log:
I0425 00:08:29.282217 1 log.go:16] 21:S 25 Apr 2024 00:08:29.282 * Migrating to orphaned master 4d1d61c90d7bf0678bf9d38ad2eee127cdc73736.

However with cluster-migration-barrier still set to 1, i assume the other replica should have failed over it;s primary for any issues.

In this scenario, is it a good decision to set cluster-allow-replica-migration to no? What the advantages and disadvantages. Any detailed insight into this configuration will be very helpful, Thanks!

Generally, questions about using Redis should be directed to the community:

• the mailing list
• the redis tag at StackOverflow
• /r/redis subreddit
• github discussions

It is also possible that your question was already asked here, so please do a quick issues search before submitting. Lastly, if your question is about one of Redis' clients, you may to contact your client's developers for help.

That said, please feel free to replace all this with your question :)