Behaviour when all redis nodes go down simultaneously.

[rahulKrishnaM]

Behaviour when all redis nodes go down simultaneously.

[bjosv]

Interesting, as of now you assessment that a re-initialization is needed in this scenario is correct.
The initially given addresses are replaced with the knowledge (addresses) from the Redis cluster.

Is this triggered by tests or is it a likely scenario with the Redis operator you are using?

What do you believe is the best way to handle this scenario?
Should the initially added nodes be kept and used as a last resort when attempting to get the slot information from the cluster.
..or should there be an additional API for this?

[rahulKrishnaM]

Ya as part of some resiliency tests, this particular scenario was attempted.

I was thinking storing the k8s fqdn/ip which is initially passed to hiredis-cluster in the cache would be the best option. Since service is not bound to change at any point (for power failure sort of scenarios), if we tag that to the current cluster discovery mechanism, we could fallback to the k8s service if all the previously learned nodes return an error or something like that.