ERR FAILOVER requires connected replicas.: FAILOVER requires connected replicas
RedisWhat does it mean?
FAILOVER was run to start a coordinated (graceful) failover, but it was rejected because no suitable replica connected to the primary is available to take over. Failover cannot happen without a target to hand the role to.
Why does it happen?
The primary currently has no connected replicas (replicas are down, disconnected from the network or not in sync), or the specified target replica is not eligible/connected. When manual FAILOVER (Redis 6.2+) is called, the replication topology does not meet the required condition. Note: FAILOVER works only with standalone (master/replica) replication; in Redis Cluster, CLUSTER FAILOVER is used on the replica.
How to fix it
Make sure at least one healthy, connected and up-to-date replica exists (check connected_slaves and sync status with INFO replication). Fix network/access issues on the replicas so they connect to the primary. To fail over to a specific target, use FAILOVER TO host port and verify that replica is eligible.
More from this engine
- ERR Background append only file rewriting already in progressAOF rewrite already in progress
- IOERR error or timeout reading from target instanceMIGRATE: I/O error or timeout to target
- ERR Error compiling script (new function)Error compiling Lua script
- ERR invalid expire time in 'set' commandinvalid expire time in SET