When master1 down, slave master liters, if in the process the client request over redis.clients.jedis.exceptions.JedisClusterMaxRedirectionsException occur: Too many Cluster redirections abnormality (herein will retry 5 times), when the ascending slave1 after, grooves key slot will be pushed to slave1, the operation key when the client again, the client uses the new upgrade jedisPool up master connection operation, when a new master upgrade and then hung up to die, the lost 1/3 data.
Thinking redis one master node downtime caused
Guess you like
Origin blog.csdn.net/nmjhehe/article/details/103538808
Recommended
Ranking