cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cliff Moon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1428) Rejecting keyspace creation when RF > N is incorrect
Date Tue, 21 Sep 2010 16:36:35 GMT

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

Cliff Moon commented on CASSANDRA-1428:
---------------------------------------

This ticket was specifically in reference to creation of a keyspace with RF > N.  Since
all of the schema stuff now is the responsibility of an api client instead of a config, it
would require clients to make different schemas say if they were in a testing environment
with fewer machines than production.



> Rejecting keyspace creation when RF > N is incorrect
> ----------------------------------------------------
>
>                 Key: CASSANDRA-1428
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1428
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7 beta 1
>            Reporter: Cliff Moon
>            Priority: Minor
>             Fix For: 0.7.0
>
>
> The behavior introduced in this patch http://www.mail-archive.com/commits@cassandra.apache.org/msg05913.html
is incorrect.
> Disallowing keyspace creation when RF > N is semantically incorrect and makes both
scaling a cluster up and down more difficult than it should be.  This is compounded by the
current lack of any API methods to change the replication factor.  Most dynamo style systems
allow RF to be set > N for smaller clusters.  The cluster will behave as if RF = N until
enough nodes are added such that RF < N.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message