[
https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137509#comment-13137509
]
Jonathan Ellis commented on CASSANDRA-2506:
-------------------------------------------
bq. I'm also afraid that the configuration options as implemented by this patch
will be a bit confusing for people. The fact that read_repair_chance concern
repair on the whole cluster while read_repair_chance_options concerns repair
local to the cluster in particular and the fact that read_repair_chance has
"priority" over the dc options.
What if we had {{read_repair_chance}} and {{read_repair_datacenters}}? Not
quite as flexible but it covers the known use cases without being confusing.
> 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.2
>
> Attachments: 0001-dc-localized-read-repair.patch,
> 0002-thrift-and-avro.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
