cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8086) Cassandra should have ability to limit the number of native connections
Date Tue, 03 Feb 2015 18:48:37 GMT


Benedict commented on CASSANDRA-8086:

We expect them to generally persist a while, but that will be usecase dependent. It's unlikely
to be a bottleneck either way, but there's no great reason not to use a ConcurrentHashMap,
and perhaps an AtomicLong instead of a Long which also helps avoid boxing. 

> Cassandra should have ability to limit the number of native connections
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-8086
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Vishy Kasar
>            Assignee: Norman Maurer
>             Fix For: 2.1.3, 2.0.13
>         Attachments: 0001-CASSANDRA-8086-Allow-to-limit-the-number-of-native-c-2.0.patch,
0001-CASSANDRA-8086-Allow-to-limit-the-number-of-native-c.patch, 0001-CASSANDRA-8086-Allow-to-limit-the-number-of-native-c.txt
> We have a production cluster with 72 instances spread across 2 DCs. We have a large number
( ~ 40,000 ) of clients hitting this cluster. Client normally connects to 4 cassandra instances.
Some event (we think it is a schema change on server side) triggered the client to establish
connections to all cassandra instances of local DC. This brought the server to its knees.
The client connections failed and client attempted re-connections. 
> Cassandra should protect itself from such attack from client. Do we have any knobs to
control the number of max connections? If not, we need to add that knob.

This message was sent by Atlassian JIRA

View raw message