Listing any node in the initialization of the cluster in the client is enough to be able to properly connect to the specified database.
Each node in the cluster contains the full topology of all databases and all nodes that are in the cluster.
Nevertheless, it is possible to specify multiple node urls at the initialization. But why list multiple the nodes in the cluster, if url of any cluster node will do?
By listing multiple the nodes in the cluster, we can ensure that if a single node is down and we bring a new client up, we'll still be able to get the initial topology. If the cluster sizes are small (three to five nodes), we'll typically list all the nodes in the cluster. But for larger clusters, we'll usually just list enough nodes that having them all go down at once will mean that you have more pressing concerns then a new client coming up.
const store = new DocumentStore([
"http://[node A url]",
"http://[node B url]",
"http://[node C url]"
// the rest of ClientAPI code