Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: <CAJpqPhjeTTG_w675uhO_nkBrs3y7zyy+Br6nRgLO_gpWTmDk=A@mail.gmail.com>
References: <CAJpqPhjeTTG_w675uhO_nkBrs3y7zyy+Br6nRgLO_gpWTmDk=A@mail.gmail.com>
From: Alain RODRIGUEZ <arodrime@gmail.com>
Date: Wed, 11 May 2016 16:12:15 +0200
Message-ID: <CA+VSrLrk8vhHhM9sbuUA4_FgGPO3FGgkKqeKthkmik8y4AzyQQ@mail.gmail.com>
Subject: Re: Re : Optimum value for native_transport_max_concurrent_connections
 and native_transport_max_concurrent_connections_per_ip
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a1142f7d81a759f053291a22c
archived-at: Wed, 11 May 2016 14:12:41 -0000

--001a1142f7d81a759f053291a22c
Content-Type: text/plain; charset=UTF-8

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  C*2.1, nodetool tpstats outputs the number of blocked native
requests, allowing to better tune the
native_transport_max_concurrent_connections.

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,

C*heers,
-----------------------
Alain Rodriguez - alain@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-04-29 16:39 GMT+02:00 sai krishnam raju potturi <pskraju88@gmail.com>:

> 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
>

--001a1142f7d81a759f053291a22c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>tl;dr: Would you like to give Cassa=
ndra 2.1 a try?</div><div><br></div><div>Longer answer:</div><div><br></div=
><div>With the good versions of both the driver and Cassandra, you could be=
 using the V3 protocol, which dramatically improved way connections work.</=
div><div><br></div><div><a href=3D"http://www.datastax.com/dev/blog/java-dr=
iver-2-1-2-native-protocol-v3">http://www.datastax.com/dev/blog/java-driver=
-2-1-2-native-protocol-v3</a><br></div><div><br></div><div>Also, in =C2=A0C=
*2.1, nodetool tpstats outputs the number of blocked native requests, allow=
ing to better tune the native_transport_max_concurrent_connections.</div><d=
iv><br></div><div>If you don&#39;t want to upgrade to 2.1, just try tuning =
the number of connection on the client side and monitor. About native_trans=
port_max_concurrent_connections, as for other parameters, starting from def=
aults and monitoring the changes, working as much as possible on a canary n=
ode is often the best way to go.</div><div><br></div><div>Hope this helps,<=
/div><div><br></div><div>C*heers,</div><div><div>-----------------------</d=
iv><div>Alain Rodriguez - <a href=3D"mailto:alain@thelastpickle.com">alain@=
thelastpickle.com</a></div><div>France</div><div><br></div><div>The Last Pi=
ckle - Apache Cassandra Consulting</div><div><a href=3D"http://www.thelastp=
ickle.com">http://www.thelastpickle.com</a></div></div></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">2016-04-29 16:39 GMT+02:00 sai =
krishnam raju potturi <span dir=3D"ltr">&lt;<a href=3D"mailto:pskraju88@gma=
il.com" target=3D"_blank">pskraju88@gmail.com</a>&gt;</span>:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div dir=3D"ltr"><span style=3D"font-size:12.8px">hi;<=
/span><div style=3D"font-size:12.8px">=C2=A0 we are upgrading our cluster f=
rom=C2=A0<span style=3D"background-color:rgb(255,255,0)">apache-cassandra 2=
.0.14</span>=C2=A0to=C2=A0<span style=3D"background-color:rgb(255,255,0)">2=
.0.17</span>. We have been facing=C2=A0<span style=3D"background-color:rgb(=
255,255,0)">SYN flooding issue</span>=C2=A0(port 9042) in our current versi=
on of Cassandra at times. We are hoping to tackle the SYN flooding issues w=
ith the following attributes in the YAML file for 2.0.17=C2=A0</div><div st=
yle=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px"><span st=
yle=3D"background-color:rgb(255,255,0)">native_transport_max_concurrent_con=
nections</span><br></div><div style=3D"font-size:12.8px"><br></div><div sty=
le=3D"font-size:12.8px"><span style=3D"background-color:rgb(255,255,0)">nat=
ive_transport_max_concurrent_connections_per_ip<br></span></div><div style=
=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px"><br></div><=
div style=3D"font-size:12.8px">Are there any=C2=A0<span style=3D"background=
-color:rgb(255,255,0)">observed limitations</span>=C2=A0for the above menti=
oned attributes. During the=C2=A0<span style=3D"background-color:rgb(255,25=
5,0)">peak hours</span>=C2=A0each node serves around=C2=A0<span style=3D"ba=
ckground-color:rgb(255,255,0)">1500 connections</span>. Please suggest opti=
mal values for the mentioned attributes.=C2=A0</div><div style=3D"font-size=
:12.8px"><br></div><div style=3D"font-size:12.8px"><br></div><div style=3D"=
font-size:12.8px">thanks</div></div>
</blockquote></div><br></div>

--001a1142f7d81a759f053291a22c--