[
https://issues.apache.org/jira/browse/CASSANDRA-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743438#comment-14743438
]
Paulo Motta commented on CASSANDRA-7392:
----------------------------------------
bq. I propose to log at WARN a generic message such as some CQL queries timed
out using the no spam logger to avoid polluting the main log file. Then, we log
the full details at DEBUG level by either adding a new appender writing to
query.log or by using debug.log.
+1, since it will print important warning information on system.log, and more
detailed troubleshooting info on debug.log. but I'd rather reuse debug.log
instead of adding a new appender (query.log). you can leave it as DEBUG with
the current appender, and it will automatically go to debug.log after
CASSANDRA-10241
> Abort in-progress queries that time out
> ---------------------------------------
>
> Key: CASSANDRA-7392
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7392
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Stefania
> Priority: Critical
> Fix For: 3.x
>
>
> Currently we drop queries that time out before we get to them (because node
> is overloaded) but not queries that time out while being processed.
> (Particularly common for index queries on data that shouldn't be indexed.)
> Adding the latter and logging when we have to interrupt one gets us a poor
> man's "slow query log" for free.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
