Re: Don't print Ping caused error logs

The driver had load balancing policies built in. Behind a load balancer you'd lose the benefit things like the TokenAwarePolicy. On Mon, Jun 19, 2017 at 3:49 PM Jonathan Haddad wrote: > The driver grabs all the cluster information from the nodes you provide > the driver and

Re: Don't print Ping caused error logs

The driver grabs all the cluster information from the nodes you provide the driver and connects automatically to the rest. You don't need (and shouldn't use) a load balancer. Jon On Mon, Jun 19, 2017 at 12:28 PM Daniel Hölbling-Inzko < daniel.hoelbling-in...@bitmovin.com> wrote: > Just out of

Re: Don't print Ping caused error logs

Just out of curiosity how to you then make sure all nodes get the same amount of traffic from clients without having to maintain a manual contact points list of all cassandra nodes in the client applications? Especially with big C* deployments this sounds like a lot of work whenever

Re: Don't print Ping caused error logs

Just in case you are not aware using a load balancer is an anti patter. Please refer to (http://docs.datastax.com/en/landing_page/doc/landing_page/planning/planningAntiPatterns.html#planningAntiPatterns__AntiPatLoadBal

Don't print Ping caused error logs

Hi, Our cluster nodes are behind a SLB(Service Load Balancer) with a VIP and the Cassandra client access the cluster by the VIP. System.log print the below IOException every several seconds. I guess it's the SLB service which Ping the port 9042 of the Cassandra node periodically and caused the