Re: Re : Optimum value for native_transport_max_concurrent_connections and native_transport_max_concurrent_connections_per_ip

thanks Alain. We were planning to move to 2.0.17 to begin with, and later move to 2.1. We will try tweaking the number of connections from the application side to begin with. thanks Sai On Wed, May 11, 2016 at 10:12 AM, Alain RODRIGUEZ wrote: > Hi, > > tl;dr: Would you like

Re: Re : Optimum value for native_transport_max_concurrent_connections and native_transport_max_concurrent_connections_per_ip

Hi, tl;dr: Would you like to give Cassandra 2.1 a try? Longer answer: With the good versions of both the driver and Cassandra, you could be using the V3 protocol, which dramatically improved way connections work. http://www.datastax.com/dev/blog/java-driver-2-1-2-native-protocol-v3 Also, in

Re : Optimum value for native_transport_max_concurrent_connections and native_transport_max_concurrent_connections_per_ip

hi; we are upgrading our cluster from apache-cassandra 2.0.14 to 2.0.17. We have been facing SYN flooding issue (port 9042) in our current version of Cassandra at times. We are hoping to tackle the SYN flooding issues with the following attributes in the YAML file for 2.0.17

Re : Optimum value for native_transport_max_concurrent_connections and native_transport_max_concurrent_connections_per_ip

hi; we are upgrading our cluster from apache-cassandra 2.0.14 to 2.0.17. We have been facing SYN flooding issue (port 9042) in our current version of Cassandra at times. We are hoping to tackle the SYN flooding issues with the following attributes in the YAML file for 2.0.17