client: for read accesses, pick a random good node, connected or not
The issue was that at startup, or after nodes are back, the previous code prevented full load balancing until some data are written. It was like this to limit the number of connections, which does not matter anymore (see commit 77132157).
Showing
Please register or sign in to comment