You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2010/10/05 15:09:34 UTC

[jira] Issue Comment Edited: (CASSANDRA-1428) Rejecting keyspace creation when RF > N is incorrect

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

Gary Dusbabek edited comment on CASSANDRA-1428 at 10/5/10 9:08 AM:
-------------------------------------------------------------------

How about a system test that verifies that a keyspace with RF > N can be created?  With this patch SS.loadSchemaFromYAML() doesn't work when RF > N.

      was (Author: gdusbabek):
    How about a system test that verifies that a keyspace with RF > N can be created?  +1 otherwise.
  
> 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
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: 1428.txt
>
>
> 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.