[ https://issues.apache.org/jira/browse/CASSANDRA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986516#action_12986516 ]
Jonathan Ellis commented on CASSANDRA-982: ------------------------------------------ Moved to CASSANDRA-2051 since this is not related to -982. > read repair on quorum consistencylevel > -------------------------------------- > > Key: CASSANDRA-982 > URL: https://issues.apache.org/jira/browse/CASSANDRA-982 > Project: Cassandra > Issue Type: New Feature > Components: Core > Reporter: Jonathan Ellis > Assignee: Jonathan Ellis > Priority: Minor > Fix For: 0.7.1 > > Attachments: > 0001-better-digest-checking-for-ReadResponseResolver.patch, > 0001-r-m-SP.weakRead-rename-strongRead-to-fetchRows.-read-r.txt, > 0002-implement-read-repair-as-a-second-resolve-after-the-in.txt, > 0002-quorum-only-read.txt, > 0003-rename-QuorumResponseHandler-ReadCallback.txt, > 982-resolve-digests-v2.txt, rep_fix_01.patch, rep_fix_02.patch > > Original Estimate: 6h > Remaining Estimate: 6h > > CASSANDRA-930 made read repair "fuzzy optional," but this only helps with > ConsistencyLevel.ONE: > - Quorum reads always send requests to all nodes > - only the first Quorum's worth of responses get compared > So what we'd like to do two changes: > - only send read requests to the closest R live nodes > - if read repair is enabled, also compare results from the other nodes in the > background -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.