[
https://issues.apache.org/jira/browse/CASSANDRA-16747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16747:
-----------------------------------------
Resolution: Won't Fix
Status: Resolved (was: Triage Needed)
This has been raised before (I think I may have even done it) but there are
some who actually prefer to create the KS before adding nodes, and there other
cases to consider, like when rf=N and you want to remove a node... removing the
flexibility here simply isn't worth it.
> Block creating keyspace with RF > Cassandra node count
> ------------------------------------------------------
>
> Key: CASSANDRA-16747
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16747
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema
> Reporter: Tri Nguyen
> Priority: Normal
>
>
> Using Cassandra 3.11.10, 3 nodes cluster Cassandra allows to create a
> keyspace having `replication_factor` greater than the number of available
> nodes.
>
> {code:java}
> -- successfully created Keyspace with RF = 3 > node count = 3
> CREATE KEYSPACE mykeyspace WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': 5 };
> {code}
> From [this
> discussion|https://community.datastax.com/questions/11623/create-keyspace-with-rf-physical-cassandra-node-co.html]
> on community.datastax.com. It appears that this would lead to serious
> operational problems.
> Would it be OK to improve the `CREATE KEYSPACE` to block (or display warning)
> when attempting to set `replication_factor` > node count?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
