The problem/use-case that the feature addresses
Discuss about the issue: https://github.com/redis/redis/issues/12527, when combining 2 redis clusters with same slots and have leader alone. We can not assign to the expect redis cluster leader.
Description of the feature
When we config the 'cluster-replica-no-failover yes', even though the sender redis is master . But as it config the 'cluster-replica-no-failover yes', it should not change the slots in clusterUpdateSlotsConfigWith() funciton. And the sender shouldnot become the leader anyways.
Alternatives you've considered
I try to change the configEpoch in the 2 redis cluster , which the 1st redis all nodes configEpoch lager than the 2nd currentEpoch. But i found that it is too efficient for us to change it. Because we need to change our every shard with leader about the 1st redis configEpoch.
Additional information
I think when we use 2 Completely redis cluster and with same slots. We can assign to the expect redis cluster leader by 'cluster-replica-no-failover yes' config which already exits.
Thanks. jarvif
Comment From: Jarvif
More importantly , the configEpoch can not set a number but only increase by CLUSTER BUMPEPOCH when current node know any other node. It also will be too efficient for us.
Comment From: Jarvif
@madolson @oranagra
Comment From: madolson
I'm still not sure there is a very common use case. I'm okay leaving this open as a feature, but I don't think we are likely ever going to work on it.
Comment From: Jarvif
已收到，谢谢。