[
https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2506:
--------------------------------------
Affects Version/s: (was: 1.0.1)
Fix Version/s: (was: 1.0.7)
1.1
{quote}
Basically there has been 2 proposition of enhancements for RR on this ticket:
# Being able to completely exlude a given DC of any RR
# Have a different chance of repair for intra-DC and inter-DC RR
{quote}
You're right. I think what we really want is (2) ... on a per-DC basis. That
is, DC A might want intra-DC RR chance at X and cross-DC chance at Y, but DC B
might want them at V and W.
Looking back, I think the main problem with the initial patch was the poorly
defined interation between global read_repair_chance and per-DC settings. In
which case, dropping the global r_r_c seems like a reasonable simplification,
especially as part of 1.1 (which is where we should be doing new features
anyway).
If we think per-DC settings are too complicated in any form, then I'd be okay
with the different-cross-DC chance approach as an 80% solution.
> 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
> Reporter: Brandon Williams
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.1
>
> Attachments: 0001-dc-localized-read-repair-v2.patch,
> 0001-dc-localized-read-repair.patch,
> 0001-documentation-for-read_repair-v4.patch,
> 0001-thrift-and-avro-changes-v3.patch,
> 0002-dc-localized-read-repair-v3.patch, 0002-thrift-and-avro-v2.patch,
> 0002-thrift-and-avro-v4.patch, 0002-thrift-and-avro.patch,
> 0003-dc-localized-read-repair-v4.patch,
> 0003-documentation-for-read_repair-v3.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
