[
https://issues.apache.org/jira/browse/CASSANDRA-10789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467993#comment-16467993
]
Ben Bromhead edited comment on CASSANDRA-10789 at 5/8/18 9:34 PM:
------------------------------------------------------------------
I agree with your point on having it query-able (e.g. I would advocate doing
via JMX, again to keep things simple).
CASSANDRA-13985 - Can do similar things but at the user level. I wish
application that used Cassandra would ensure each client instance had an
individual user set of credentials and rotated secrets etc, but based on our
experience this is not normally the case.
The current suite of tools and admin commands that Cassandra supports at the
moment pushes this kind of coordination to external tools and I'm not sure it's
worth waiting for internal management of cluster wide commands unless they are
just round the corner (which would be awesome).
was (Author: benbromhead):
I agree with your point on having it query-able (e.g. I would advocate doing
via JMX, again to keep things simple).
CASSANDRA-13985 - Can do similar things but at the user level. I wish each
client instance had an individual user and rotated credentials, but this is not
normally the case.
The current suite of tools and admin commands that Cassandra supports at the
moment pushes this kind of coordination to external tools and I'm not sure it's
worth waiting for internal management of cluster wide commands unless they are
just round the corner (which would be awesome).
> Allow DBAs to kill individual client sessions without bouncing JVM
> ------------------------------------------------------------------
>
> Key: CASSANDRA-10789
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10789
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination
> Reporter: Wei Deng
> Assignee: Damien Stevenson
> Priority: Major
> Fix For: 4.x
>
> Attachments: 10789-trunk-dtest.txt, 10789-trunk.txt
>
>
> In production, there could be hundreds of clients connected to a Cassandra
> cluster (maybe even from different applications), and if they use DataStax
> Java Driver, each client will establish at least one TCP connection to a
> Cassandra server (see
> https://datastax.github.io/java-driver/2.1.9/features/pooling/). This is all
> normal and at any given time, you can indeed see hundreds of ESTABLISHED
> connections to port 9042 on a C* server (from netstat -na). The problem is
> that sometimes when a C* cluster is under heavy load, when the DBA identifies
> some client session that sends abusive amount of traffic to the C* server and
> would like to stop it, they would like a lightweight approach rather than
> shutting down the JVM or rolling restart the whole cluster to kill all
> hundreds of connections in order to kill a single client session. If the DBA
> had root privilege, they would have been able to do something at the OS
> network level to achieve the same goal but oftentimes enterprise DBA role is
> separate from OS sysadmin role, so the DBAs usually don't have that privilege.
> This is especially helpful when you have a multi-tenant C* cluster and you
> want to have the impact for handling such client to be minimal to the other
> applications. This feature (killing individual session) seems to be a common
> feature in other databases (regardless of whether the client has some
> reconnect logic or not). It could be implemented as a JMX MBean method and
> exposed through nodetool to the DBAs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
