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 use AWS Elasticache Valkey and recently migrated one of our ReplicationGroups to Cluster-compatible mode to distribute the load.
From time to time, we see our clients entering the aforementioned loop with both master.length = 0 and replicas.length = 0 and endlessly spinning completely pegging the CPU.
We have tried using Elasticache's primary endpoint, configuration endpoint and node endpoints to no luck. We are not sure why AWS returns 0 masters/replicas but regardless, code shouldn't even enter this loop when both replicas and masters are empty.
Because when the clients enter this state, it is irrecoverable.