[ https://issues.apache.org/jira/browse/CASSANDRA-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913053#action_12913053 ]
Gary Dusbabek commented on CASSANDRA-1428: ------------------------------------------ I interpreted "RF to be set > N for smaller clusters" as meaning, "let high-CL writes succeed even though we don't have enough nodes to support the RF when N is small." I don't think we should allow that. >From an syspop pov, I think we should allow the creation of keyspaces where RF >> N. There is no harm in this for new keyspaces where there is nothing to >stream. > 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.