cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alain RODRIGUEZ <>
Subject Re: Re : Optimum value for native_transport_max_concurrent_connections and native_transport_max_concurrent_connections_per_ip
Date Wed, 11 May 2016 14:12:15 GMT

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.

Also, in  C*2.1, nodetool tpstats outputs the number of blocked native
requests, allowing to better tune the

If you don't want to upgrade to 2.1, just try tuning the number of
connection on the client side and monitor. About
native_transport_max_concurrent_connections, as for other parameters,
starting from defaults and monitoring the changes, working as much as
possible on a canary node is often the best way to go.

Hope this helps,

Alain Rodriguez -

The Last Pickle - Apache Cassandra Consulting

2016-04-29 16:39 GMT+02:00 sai krishnam raju potturi <>:

> 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
> native_transport_max_concurrent_connections
> native_transport_max_concurrent_connections_per_ip
> Are there any observed limitations for the above mentioned attributes.
> During the peak hours each node serves around 1500 connections. Please
> suggest optimal values for the mentioned attributes.
> thanks

View raw message