garnet icon indicating copy to clipboard operation
garnet copied to clipboard

Cluster node does not update announcing ip after move

Open Defman opened this issue 1 year ago • 1 comments

Describe the bug

Reported cluster node ips via cluster nodes are not in sync with the actual ips.

Steps to reproduce the bug

  1. Create cluster on k8s
  2. Move pod to new node
  3. 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

Defman avatar Sep 05 '24 12:09 Defman

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?

vazois avatar Sep 24 '24 18:09 vazois

Another solution would be for kubernetes to rely on dns hostname instead of IPs like proposed in #741

ecyrbe avatar Oct 22 '24 13:10 ecyrbe

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?

I am wondering if the above helped somehow?

vazois avatar Jan 21 '25 19:01 vazois