You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alwyn Davis (JIRA)" <ji...@apache.org> on 2016/09/12 06:57:20 UTC

[jira] [Updated] (CASSANDRA-12629) All Nodes Replication Strategy

     [ https://issues.apache.org/jira/browse/CASSANDRA-12629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alwyn Davis updated CASSANDRA-12629:
------------------------------------
    Attachment: 12629-3.7.patch

I'm attaching an implementation of AllStrategy.

I believe that this issue is pretty straightforward and am in the process of writing the test cases. However, I'd appreciate any feedback on on this approach.

> All Nodes Replication Strategy
> ------------------------------
>
>                 Key: CASSANDRA-12629
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12629
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Alwyn Davis
>            Priority: Minor
>             Fix For: 3.7
>
>         Attachments: 12629-3.7.patch
>
>
> When adding a new DC, keyspaces must be manually updated to replicate to the new DC.  This is problematic for system_auth, as it cannot achieve LOCAL_ONE consistency (for a non-cassandra user), until its replication options have been updated on an existing node.
> Ideally, system_auth could be set to an "All Nodes strategy" that will replicate it to all nodes, as they join the cluster.  It also removes the need to update the replication factor for system_auth when adding nodes to the cluster to keep with the recommendation of RF=number of nodes (at least for small clusters).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)