[
https://issues.apache.org/jira/browse/CASSANDRA-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944319#comment-14944319
]
Stefania commented on CASSANDRA-7392:
-------------------------------------
Thanks for spending the time to understand the problem with logging.
bq. So you set the filter in the logging to be more permissive, but only have
the monitoring logger running at debug? The other loggers won't emit debug
statements?
Correct.
bq. It looks like the NanoTimeToCurrentTimeMillis test can't check the
condition it was checking before which was that it kinda sort of work to try
and propagate NTP updates. You could have the test submit the update task to
the STPE instead of notifying it. That could be a function in
NanoTimeToCurrentTimeMillis so the details aren't foisted onto the test.
See if [this
is|https://github.com/stef1927/cassandra/commit/fc42b1e684649fc1cf9499e72c643d5c2a31455d]
what you meant.
> 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)
