You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
I am working with the ClusterClient and I'm getting an unexpected behavior when a Master node is being shutdown. I have the MaxRetries set at 2. When the Master node is being shutdown, I'm getting the following error -> dial tcp xxx.xx.xxx.xxx:xxxx: connect: connection refused
The first retry is done on the same node as expected, but when it comes to the second retry, it is marking the node as failing before retrying. I would expected the client to try on a different node, but it's trying on the same node and failing again for a third time. I do see that my client is correctly aware of multiple nodes (Masters and Slaves) when I ping them using ForEachMaster() and ForEachSlave(), but it always sticks to the same node when retrying.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello!
I am working with the ClusterClient and I'm getting an unexpected behavior when a Master node is being shutdown. I have the MaxRetries set at 2. When the Master node is being shutdown, I'm getting the following error ->
dial tcp xxx.xx.xxx.xxx:xxxx: connect: connection refused
The first retry is done on the same node as expected, but when it comes to the second retry, it is marking the node as failing before retrying. I would expected the client to try on a different node, but it's trying on the same node and failing again for a third time. I do see that my client is correctly aware of multiple nodes (Masters and Slaves) when I ping them using ForEachMaster() and ForEachSlave(), but it always sticks to the same node when retrying.
Any idea what is the issue?
Beta Was this translation helpful? Give feedback.
All reactions