-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed
Description
It seems that after calling ConnectionMultiplexer.ReconfigureAsync() only new server nodes could be discovered and added to ServerSnapshot list but old ones are never removed.
We have a situation when Redis Cluster nodes got new IP addresses after rescheduling in Kubernetes cluster. They are successfully discovered by client but old phantom IPs stay in server list.
Is there a way to detect such non-responsive IPs and remove corresponding servers from the snapshot? Or is ForceReconnect approach the recommended way of handling this situation?
Metadata
Metadata
Assignees
Labels
No labels