You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2016/12/16 06:25:58 UTC

[jira] [Created] (CASSANDRA-13050) ReadCommand.CheckForAbort not monitoring CQL rows for range queries

Stefania created CASSANDRA-13050:
------------------------------------

             Summary: ReadCommand.CheckForAbort not monitoring CQL rows for range queries
                 Key: CASSANDRA-13050
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13050
             Project: Cassandra
          Issue Type: Bug
          Components: Local Write-Read Paths
            Reporter: Stefania
            Assignee: Stefania
             Fix For: 3.x


If I understood the iterator transformations introduced by CASSANDRA-9975 correctly, [ReadCommand.CheckForAbort|https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/db/ReadCommand.java#L541] should apply itself before returning a partition. At the moment it is applied to row iterators for single command partitions, but for range queries I think it only monitors the query progress when a new partition is iterated, not when a new row is iterated. So for large partitions, we may fail to log a query as slow, or fail to abort it if the RPC timeout is exceeded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)