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

Vijay commented on CASSANDRA-2506:
----------------------------------

I agree that this is not interesting in 1.1, but there are occasional chances 
of loosing of a CL or bad blocks remains. Manual Repair seem to be better in 
1.1 too...

Currently enabling RR in Multi dc/region is almost unusable (throughput is very 
low on the cluster). so if we support it and if the users use it, it will be 
better to support RR for local DC.

I like the idea of just 2 settings global and local RR, let me know if you 
think otherwise. Thanks!
                
> Push read repair setting down to the DC-level
> ---------------------------------------------
>
>                 Key: CASSANDRA-2506
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2506
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.0.1
>            Reporter: Brandon Williams
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.0.3
>
>         Attachments: 0001-dc-localized-read-repair-v2.patch, 
> 0001-dc-localized-read-repair.patch, 0002-thrift-and-avro-v2.patch, 
> 0002-thrift-and-avro.patch, 
> 0003-documentation-for-read_repair_options-v2.patch, 
> 0003-documentation-for-read_repair_options.patch
>
>
> Currently, read repair is a global setting.  However, when you have two DCs 
> and use one for analytics, it would be nice to turn it off only for that DC 
> so the live DC serving the application can still benefit from it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to