cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-9502) Range-slice queries with CL>ONE do unnecessary read-repairs
Date Thu, 28 May 2015 22:07:17 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Stupp resolved CASSANDRA-9502.
-------------------------------------
       Resolution: Duplicate
    Reproduced In: 2.0.14  (was: 2.0.11)

Well - spent some hours on this to finally build a [dtest that repros on 2.0.11...2.0.14|https://github.com/snazy/cassandra-dtest/tree/9502-wrong-read-repair]
to finally 

> Range-slice queries with CL>ONE do unnecessary read-repairs
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-9502
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9502
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>            Priority: Minor
>
> Scenario:
> * keyspace with RF>1
> * table filled with data (no tombstones)
> * CL QUORUM (anything > ONE)
> * {{select * from table}} (range-slice)
> * trace output looks fine
> * create some tombstones (e.g. {{delete from table where key = foo}})
> * {{select * from table}} (range-slice)
> * trace output shows mutations (RR)
> That RR is triggered from {{RangeSliceResponseResolver.Reducer.getReduced}}.
> Seems like a live-cell-count comparison is missing.
> Will create a dtest to prove the behavior and probably a patch.
> NB: {{RowDataResolver}} and {{RowDigestResolver}} are fine.



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

Mime
View raw message