Very nice - Thanks Jack. I was looking at the docs and Contact Points but didn't see this. I'll use DNS records to manage the main contact points and update the DNS when those servers change.
We should catch up again soon. Last time was a few years ago at the bar with Jake. On Tue, Feb 2, 2016 at 10:58 AM, Jack Krupansky <jack.krupan...@gmail.com> wrote: > No need to restart. As per the doc for Node Discovery: > "The driver discovers the nodes that constitute a cluster by querying the > contact points used in building the cluster object. After this it is up to > the cluster's load balancing policy to keep track of node events (that is > add, down, remove, or up) by its implementation of the Host.StateListener > interface." > > See: > > http://docs.datastax.com/en/developer/java-driver/3.0/common/drivers/reference/nodeDiscovery_r.html > > That said, your client would need to be modified/reconfigured and > restarted if the contact points changed enough that none were accessible. > > > -- Jack Krupansky > > On Tue, Feb 2, 2016 at 10:47 AM, Richard L. Burton III <mrbur...@gmail.com > > wrote: > >> In the case of adding more nodes to the cluster, would my application >> have to be restarted to detect the new nodes (as opposed to a node acting >> like a coordinator). >> >> e.g., Having the Java code connect using 3 known contact points and when >> a 4th and 5th node are added, the driver will become aware of these nodes >> without havng to be restarted? >> >> -- >> -Richard L. Burton III >> @rburton >> > > -- -Richard L. Burton III @rburton
