[
https://issues.apache.org/jira/browse/CASSANDRA-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741409#comment-14741409
]
Ariel Weisberg commented on CASSANDRA-7392:
-------------------------------------------
bq. It should be fairly straightforward to split them out into a separate file
w/ logback config if the user wants that, right?
My concern is that excessive output will roll system.log. If you log a big
enough thing every 5 seconds for long enough it can happen. We have constrained
the size a bit, but five seconds is still kind of often. I would be comfortable
with it I guess and we can always tune later.
This would be a good example of a case where we would put one thing in
system.log and another more detailed thing in the debug/trace log Paulo is
working on.
> 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)
