[
https://issues.apache.org/jira/browse/CASSANDRA-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-8086:
--------------------------------------
Reviewer: Brandon Williams
Description:
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.
was:
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.
> 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
>
> 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)
