cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-967) Implement Read Repair on Range Queries
Date Sun, 14 Nov 2010 12:31:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931816#action_12931816
] 

Jonathan Ellis commented on CASSANDRA-967:
------------------------------------------

bq. For consistency ONE the READ-REPAIR header is sent and the responding node performs a
consistency check on each row after sending the response back

This isn't quite right -- it will miss repairing any rows that don't exist on the first node
at all.

I think the right approach is to finish CASANDRA-982, moving the RR code into the coordinator
node (instead of the data node). Then it will be easier to generalize quorum/read repair paths
across row-get and range-query paths.

> Implement Read Repair on Range Queries
> --------------------------------------
>
>                 Key: CASSANDRA-967
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-967
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.6.7
>         Environment: Linux/Mac + Cassandra
>            Reporter: Vijay
>            Priority: Minor
>             Fix For: 0.8
>
>         Attachments: 0001-basic-read-repair-for-ranges-CASSANDRA-967.patch
>
>
> Implement Read Repair on Range scans.
> The idea is: To compare each rows in the list, if the responses mismatch then send back
a message resolution for that row alone to resolve the conflicts.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message