cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7392) Abort in-progress queries that time out
Date Tue, 07 Jul 2015 09:20:05 GMT


Stefania commented on CASSANDRA-7392:

Thank you [~slebresne]. I created wrapper iterators for partitions, used in executeLocally,
and for rows, used by single partition names queries. I've also renamed {{ReadOrderGroup}}
to {{ReadExecutionController}} and added {{OpState}} there. In terms of monitoring, we just
submit one executable for each read command and we cancel it if the command finishes first.
The synchronization is done via {{OpState}}. If the query is aborted on a worker node, the
coordinator will not receive any reply. If the query is aborted locally, {{handleFailure()}}
is called.  

The patch is attached but I still need to perform some more tests. I will look for a reviewer
once the tests are completed.

> Abort in-progress queries that time out
> ---------------------------------------
>                 Key: CASSANDRA-7392
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Stefania
>             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

View raw message