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
We have Redis Cluster 6.2.6 deployed in Kubernetes with the Bitnami chart. The team shuts down and restarts daily.
From time to time the cluster comes back broken. In this case, for example, redis-redis-cluster-0 is missing the ip (noaddr)
for redis-redis-cluster-3 and vice versa. All the other nodes have the IP correctly.
The cluster remains broken until I run "cluster meet x.y.z.3 6379" to fix it.
We probably need to change our shutdown approach but I was wondering, if all the other nodes have the correct ip, why isn't the cluster able to heal itself thru gossip?
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
-
We have Redis Cluster 6.2.6 deployed in Kubernetes with the Bitnami chart. The team shuts down and restarts daily.
From time to time the cluster comes back broken. In this case, for example, redis-redis-cluster-0 is missing the ip (noaddr)
for redis-redis-cluster-3 and vice versa. All the other nodes have the IP correctly.
The cluster remains broken until I run "cluster meet x.y.z.3 6379" to fix it.
We probably need to change our shutdown approach but I was wondering, if all the other nodes have the correct ip,
why isn't the cluster able to heal itself thru gossip?
PS: I see no relevant messages/errors in the logs
redis-redis-cluster-0 - cluster nodes
redis-redis-cluster-1 - cluster nodes
redis-redis-cluster-2 - cluster nodes
redis-redis-cluster-3 - cluster nodes
redis-redis-cluster-4 - cluster nodes
redis-redis-cluster-5 - cluster nodes
Beta Was this translation helpful? Give feedback.
All reactions