Replies: 1 comment
-
Lettuce attempts to restore connections to known servers regardless of whether their role has changed or not as long as these nodes are listed in You can disable |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current Redis Cluster structure consists of 3 masters and 3 slaves. I am currently testing failover and tried shutting down one master node. It was confirmed that the slave node connected to the shut down master node was automatically promoted to master.
Additionally, I confirmed that the application continues to record logs attempting to reconnect by ReconnectinoHandler.
I understand that the default value of
autoReconnect
is true. So, the application understood that it was attempting to reconnect because the previously connected master node had been shut down.application.yml
Master & Slave nodes 1: xxx.xxx.xxx.1:1000 / xxx.xxx.xxx.2:2000
Master & Slave nodes 2: xxx.xxx.xxx.2:1000 / xxx.xxx.xxx.3:2000
Master & Slave nodes 3: xxx.xxx.xxx.3:1000 / xxx.xxx.xxx.1:2000
RedisConnectionFactory
Question1.
The question here is whether it is correct for the application to continue to post logs attempting to reconnect even if one master node is shut down and a slave node is promoted to master.
A slave node has replaced the master node, but the first master node is shut down anyway and cannot be connected, so is it safe to say this is a normal phenomenon? In fact, when I used functions related to the Redis cache in the application after the master node was shut down, it worked normally.
Judging from the ClusterTopologyRefresh log in the middle, it appears that Topology update is working normally.
Beta Was this translation helpful? Give feedback.
All reactions