cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13050) ReadCommand.CheckForAbort not monitoring CQL rows for range queries
Date Tue, 20 Dec 2016 03:44:58 GMT


Stefania commented on CASSANDRA-13050:

I've fixed a few problems with the previous patch and I've multiplexed slow and aborted query
tests 4 times with no failures:


Proposed patch (it applies without conflicts to all branches):


Dtests must run with modified dtest [branch|]
or else some slow or aborted query tests may time out since we are now applying the test delay
for every CQL row.

> ReadCommand.CheckForAbort not monitoring CQL rows for range queries
> -------------------------------------------------------------------
>                 Key: CASSANDRA-13050
>                 URL:
>             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,-
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

View raw message