cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12629) All Nodes Replication Strategy
Date Tue, 11 Oct 2016 01:40:20 GMT

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

Jeremiah Jordan commented on CASSANDRA-12629:
---------------------------------------------

AllStrategy is actually bad to use for this. Auth caches stuff to make the queries faster,
and if you do login with the default Cassandra user that uses QUORUM then you will rarely
succeed at logging in if you have a ton of nodes.
There is a reason DataStax never contributed their EverywhereStrategy to OSS, it is very easy
to screw yourself with it.

> 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.x
>
>         Attachments: 12629-trunk.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)

Mime
View raw message