[
https://issues.apache.org/jira/browse/CASSANDRA-12403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416432#comment-15416432
]
Shogo Hoshii commented on CASSANDRA-12403:
------------------------------------------
Hello [~Stefania]-san,
Thank you very much for the review and adding dtest! Very great job.
The default value of query_log_timeout_in_ms is ok for me because most of
problematic queries take more than 1,000 msec in production environment of my
company. If my team have clusters in which we have to be very sensitive to slow
queries, we can just change the configuration.
I do not have any concern about the logging interval, 5 minutes. In terms of
log level, monitoring tools can still detect slow query log by grepping its
message even though it is INFO level.
I am sorry for putting bugs, duplication log and log missing. I should have
read the code more thoroughly.
But I have learnt a lot from your comments, code and test.
I am looking forward to the patch merged!
Thank you.
> 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)
