Entry point for defining a keySpace based
on multiple contact points (Cassandra nodes).
Even though the Cassandra driver technically only
needs a single contact point and will then fetch
the metadata for all other Cassandra nodes, it is
recommended to specify more than just one contact
point in case one node is down the moment the driver
initializes.
Since the driver finds additional nodes on its own,
the initial list of contact points only needs to be
updated when you remove one of the specified contact
points, not when merely adding new nodes to the cluster.
Entry point for defining a keySpace based on multiple contact points (Cassandra nodes).
Even though the Cassandra driver technically only needs a single contact point and will then fetch the metadata for all other Cassandra nodes, it is recommended to specify more than just one contact point in case one node is down the moment the driver initializes.
Since the driver finds additional nodes on its own, the initial list of contact points only needs to be updated when you remove one of the specified contact points, not when merely adding new nodes to the cluster.