[jira] Issue Comment Edited: (CASSANDRA-982) read repair on quorum consistencylevel

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis edited comment on CASSANDRA-982 at 1/5/11 2:10 AM:
------------------------------------------------------------------

bq. This was a leftover of trying to re-use the resolver

Oops, this was actually still saving effort for the scheduled repair resolve.  I put it back with an explanation in a comment, and made the results reference a ConcurrentMap to emphasize that concurrent remove is OK.

committed.

      was (Author: jbellis):
    bq. This was a leftover of trying to re-use the resolver

Oops, this was actually still saving effort for the scheduled repair resolve.  I put it back, but made the results reference a ConcurrentMap to emphasize that concurrent remove is OK.

committed.
  
> 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
>
>   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.