How to kill running query which is affecting my cluster performance badly .
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
It isn't possible to kill long-running queries in C* since each query runs in a thread (not a separate process) and is executed in several replicas for any consistency level higher than one.
You can only determine the queries hitting your cluster if you have audit logging enabled. In Cassandra, this isn't enabled by default because it is expensive and has a significant effect on the performance of your cluster. It isn't easy to quantify the impact of audit logging because it depends on a lot of moving parts including use case, data model, access patterns, hardware configuration, etc.
Cassandra also logs slow queries by default. Queries are considered slow if they take longer than the slow query timeout in
For details, see How to I collect slow queries in Apache Cassandra 3.11.6. Cheers!
5 People are following this question.