Lines Matching refs:master
61 a slave is able to fail over its master reducing certain delays.
86 Using these features a slave can be reported by the master `INFO` output
120 Ability of slave to announce arbitrary ip/port to master.
136 Sentinel: new test unit 07 that tests master down conditions.
168 Sentinel: fix cross-master Sentinel address update.
249 of Redis Sentinel to reconfigure back the old master, after a failover,
250 when it is reachable again, as the slave of the new master. This was due
251 to the inability to talk with the old master at all.
303 pending commands properly, so the master appeared fovever down.
787 the past a slave could migrate only to a master that used to have slaves
789 if a new slave gets at least a slot, and at least one other master in the
790 cluster has a slave, then the new master is considered a valid target for
851 | Fix a possible race condition of sdown detection if the connection to master/slave/sentinel decam…
1148 1/5 of all the cluster slots from master 0 to the other 4 masters and
1149 back into the original master.
1162 Before this fix, after a complete resharding of a master slots
1163 to other nodes, the master remains empty and the slaves migrate away
1164 to other masters with non-zero nodes. However the old master now empty,
1169 new rule. When a new or old master which is empty and without slaves,
1672 even before receiving the `DEL` command from the master. This avoids