[
https://issues.apache.org/jira/browse/CASSANDRA-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745135#comment-14745135
]
Stefania commented on CASSANDRA-7392:
-------------------------------------
Thanks for the comments, I hope to resume this tomorrow.
[~aweisberg]: aside from logging at DEBUG level is there any other blocker? Do
we still retain logging of the top N entries or shall we log all timed out
queries?
bq. For writes, we are going to be retaining the queries past the timeout for
the logger. If someone has a memory utilization issue they can't fix it by
setting the timeout lower since the logger will still retain it and it runs on
it's own period.
bq. Even in a separate debug log file rolling is a concern. One bad log
statement can wipe away all the other information in a failure scenario.
I'm not sure if there is anything we can do about this?
I think we also have one failing unit test.
> 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)
