@kedaly yes clients will automatically find new servers/replicas. Technically, a client only needs to know about one live server in the cluster. Once the client connects, each time the client sends a keep-alive it will receive back an updated list of members. IIRC clients only learn about the active members of the cluster. So, in the event an active member fails and is replaced, we assume the client has additional active members to which it can connect to learn of the new active member. Indeed, this is necessarily true since a majority of the active members in the cluster must be alive to replace a failed active member. But this does men there's some time bound within which too many servers cannot fail otherwise a client can lose all the servers in the cluster. But this is true in general. If a majority of the active members in the cluster fail simultaneously they can't be replaced. In theory, if all the active nodes in a cluster were replaced in sequence fast enough that the client could not keep up with change notifications a client could lose the cluster, but in practice that's an insane scenario.