[
https://issues.apache.org/jira/browse/CASSANDRA-12403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416652#comment-15416652
]
Stefania commented on CASSANDRA-12403:
--------------------------------------
Thank you for confirming the suggested implementation.
There were some failures with the tests, mostly unrelated except for [one
failure|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12403-dtest/lastCompletedBuild/testReport/cql_tests/SlowQueryTester/local_query_test/]
with the new tests. I've fixed the failing test and launched a repeated
execution (150 times)
[here|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-dtest-multiplex/].
I've also launched the full tests a second time to shake off some of the
unrelated failures.
Before committing the patch, I would also like to a have one more person look
at it, cc [~JoshuaMcKenzie].
> Slow query detecting
> --------------------
>
> Key: CASSANDRA-12403
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12403
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Shogo Hoshii
> Assignee: Shogo Hoshii
> Attachments: sample.log, slow_query.patch, slow_query.patch
>
>
> Hello,
> In cassandra production environment, users sometimes build anti-pattern
> tables and throw queries in inefficient manners.
> So I would like to suggest a feature that enables to log slow query.
> The feature can help cassandra operators to identify bad query patterns.
> Then operators can give advices about queries and data model to users who
> don't know cassandra so much.
> This ticket is related to CASSANDRA-6226, and I focus on detecting bad query
> patterns, not aborting them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
