[
https://issues.apache.org/jira/browse/CASSANDRA-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303802#comment-14303802
]
Joshua McKenzie commented on CASSANDRA-8086:
--------------------------------------------
Fair point [~iamaleksey] - if we disable it by default and don't register it in
the pipeline unless it's enabled, I'd be comfortable with 2.0 inclusion. At
that point it's inclusion of a new feature and should have no risk on 2.0
stability.
> Cassandra should have ability to limit the number of native connections
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-8086
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8086
> 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
(v6.3.4#6332)
