[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-2506: Fix Version/s: (was: 1.2.0 beta 1) > 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.1 > > Attachments: 0001-avro-and-Thrift-2506.patch, > 0001-dc-localized-read-repair.patch, 0001-dc-localized-read-repair-v2.patch, > 0001-documentation-for-read_repair-v4.patch, > 0001-thrift-and-avro-changes-v3.patch, > 0002-dc-localized-read-repair-v3.patch, 0002-dc-local-read-repair-2506.patch, > 0002-thrift-and-avro.patch, 0002-thrift-and-avro-v2.patch, > 0002-thrift-and-avro-v4.patch, 0003-dc-localized-read-repair-v4.patch, > 0003-documentation-for-read_repair_options.patch, > 0003-documentation-for-read_repair_options-v2.patch, > 0003-documentation-for-read_repair-v3.patch, 2506-v2.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 For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[
https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-2506:
Attachment: 2506-v2.patch
In the following code:
{noformat}
if (cfmd.getDcLocalReadRepair() > chance)
{
List address = localEndpoints(ep);
// check if blockfor more than we have localep's
return address.size() >= blockfor ? address : ep;
}
{noformat}
we should default to all the endpoints if we don't have enough in the current
DC to satisfy blockfor. What we should do is include all local endpoint and
adds enough other endpoints to satisfy blockfor, but not more. Attaching
2506_v2 patch that does this (note that it would almost work to return
{{ep.subList(0, Math.min(ep.size(), blockfor))}} since ep are sorted by
proximity but but the patch don't use that since it could be possible in theory
that some node from other DC sort before local endpoint if the snitch happens
to say so)
The rebase was also missing the CQL code for the new option, v2 includes it
(for CQL 2 & 3).
Otherwise, this lgtm.
> 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.1
>
> Attachments: 0001-avro-and-Thrift-2506.patch,
> 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-local-read-repair-2506.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, 2506-v2.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0002-dc-local-read-repair-2506.patch 0001-avro-and-Thrift-2506.patch Hi Sylvain, plz find the attachement. > 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.1 > > Attachments: 0001-avro-and-Thrift-2506.patch, > 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-local-read-repair-2506.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[
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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0002-thrift-and-avro-v4.patch 0001-documentation-for-read_repair-v4.patch 0003-dc-localized-read-repair-v4.patch > 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.4 > > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0003-dc-localized-read-repair-v4.patch) > 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.4 > > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0002-thrift-and-avro-v4.patch) > 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.4 > > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0001-documentation-for-read_repair-v4.patch) > 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.4 > > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0003-dc-localized-read-repair-v4.patch 0002-thrift-and-avro-v4.patch 0001-documentation-for-read_repair-v4.patch Plz find the attachement, 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.4 > > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0001-thrift-and-avro-changes-v3.patch > 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.4 > > Attachments: 0001-dc-localized-read-repair-v2.patch, > 0001-dc-localized-read-repair.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.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0001-thrift-and-avro-changes-v3.patch) > 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.4 > > Attachments: 0001-dc-localized-read-repair-v2.patch, > 0001-dc-localized-read-repair.patch, 0002-dc-localized-read-repair-v3.patch, > 0002-thrift-and-avro-v2.patch, 0002-thrift-and-avro.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0001-thrift-and-avro-changes-v3.patch Minor change for Schema backward compatibility change is to add the default value: +33: optional double dclocal_read_repair_chance=0.0, > 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.4 > > Attachments: 0001-dc-localized-read-repair-v2.patch, > 0001-dc-localized-read-repair.patch, 0002-dc-localized-read-repair-v3.patch, > 0002-thrift-and-avro-v2.patch, 0002-thrift-and-avro.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0001-thrift-and-avro-changes-v3.patch) > 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.4 > > Attachments: 0001-dc-localized-read-repair-v2.patch, > 0001-dc-localized-read-repair.patch, 0002-dc-localized-read-repair-v3.patch, > 0002-thrift-and-avro-v2.patch, 0002-thrift-and-avro.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0001-thrift-and-avro-changes-v3.patch 0002-dc-localized-read-repair-v3.patch 0003-documentation-for-read_repair-v3.patch incorporated discussed changes with 2 settings read_repair_chance and dclocal_read_repair_chance. > 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, 0001-thrift-and-avro-changes-v3.patch, > 0002-dc-localized-read-repair-v3.patch, 0002-thrift-and-avro-v2.patch, > 0002-thrift-and-avro.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0001-dc-localized-read-repair-v2.patch 0002-thrift-and-avro-v2.patch 0003-documentation-for-read_repair_options-v2.patch Update with read_repair_datacenters as an option to have local dc repair settings. > 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-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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0002-changes-for-dc-readrepair.patch) > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0003-changes-for-cql.patch) > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: (was: 0001-changes-to-interfaces.patch) > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-2506: - Attachment: 0001-dc-localized-read-repair.patch 0002-thrift-and-avro.patch 0003-documentation-for-read_repair_options.patch attached patch incorporates all the feedbacks. Sylvain, does read_repair_option sounds good? i just was trying to find a name close to strategy_options etc... > 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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2506: -- Reviewer: slebresne (was: jbellis) > 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-changes-to-interfaces.patch, > 0002-changes-for-dc-readrepair.patch, 0003-changes-for-cql.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2506: -- Reviewer: jbellis > 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.1 > > Attachments: 0001-changes-to-interfaces.patch, > 0002-changes-for-dc-readrepair.patch, 0003-changes-for-cql.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
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[
https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay updated CASSANDRA-2506:
-
Attachment: 0001-changes-to-interfaces.patch
0002-changes-for-dc-readrepair.patch
0003-changes-for-cql.patch
The idea is to make read_repair_chance=x to be a global setting which will
allow us to specify the inter DC repair chance.
Users can add use read_repair_chance_options={DC:x, DC2:x} to tune the amount
of RR needed within a DC.
If we dont specify RRCO then global will take into effect. For a single DC
installation users can just rely on RRC
> 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
> Attachments: 0001-changes-to-interfaces.patch,
> 0002-changes-for-dc-readrepair.patch, 0003-changes-for-cql.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2506: -- Priority: Minor (was: Major) Assignee: (was: Patricio Echague) > 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 >Priority: Minor > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2506: -- Assignee: Patricio Echague (was: Brandon Williams) > 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: Patricio Echague > Fix For: 1.0 > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-2506: -- Fix Version/s: 1.0 Assignee: Brandon Williams > 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: Brandon Williams > Fix For: 1.0 > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level
[ https://issues.apache.org/jira/browse/CASSANDRA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-2506: Description: 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. (was: 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 to the live DC serving the application can still benefit from it.) > 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 > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
