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
Sorry for the delayed response.
It must be that the new pod acquires a new IP. The solution for now will be to use --clean-cluster-config flag. This way the cluster config for the pod will be generated from scratch but you will have to re-initiate meet for that node.
Can you try this and let us know if that works?
Describe the bug
Reported cluster node ips via
cluster nodes
are not in sync with the actual ips.Steps to reproduce the bug
redis-cli ... cluster nodes
Expected behavior
No response
Screenshots
No response
Release version
No response
IDE
No response
OS version
No response
Additional context
The cluster is running ipv6
The text was updated successfully, but these errors were encountered: