[
https://issues.apache.org/jira/browse/CASSANDRA-12403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423781#comment-15423781
]
Stefania commented on CASSANDRA-12403:
--------------------------------------
Thank you for the review [~thobbs] and for the initial patch [~shoshii],
committed to trunk as 6966fcda9b5ce657760dfe103e5812862306ff7a with the
following text added to NEWS.txt:
{code}
A slow query log has been added: slow queries will be logged at DEBUG
level.
For more details refer to CASSANDRA-12403 and slow_query_log_timeout_in_ms
in cassandra.yaml.
{code}
Pull request for the new tests created
[here|https://github.com/riptano/cassandra-dtest/pull/1249].
> 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
> Labels: doc-impacting
> 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)
