[
https://issues.apache.org/jira/browse/CASSANDRA-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533908#comment-16533908
]
Sumanth Pasupuleti commented on CASSANDRA-14557:
------------------------------------------------
[~jeromatron] yes it goes beyond, in the sense.
* CASSANDRA-14303 focuses on not having to mention all the required
datacenters during keyspace creation, rather leaving it to C* to figure out the
data centers, while this ticket focuses on replication factor
* default_keyspace_rf can work complementary to CASSANDRA-14303 in the sense,
if user does not specify replication_factor during keyspace creation,
default_keyspace_rf could be used.
* default_keyspace_rf would be applicable for C* system keyspace creations
(like system_auth) in addition to user created keyspaces
* required_minimum_keyspace_rf is a configuration that will prevent any
keyspace creations with an rf lower than what is configured
> Consider adding default and required keyspace replication options
> -----------------------------------------------------------------
>
> Key: CASSANDRA-14557
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14557
> Project: Cassandra
> Issue Type: Improvement
> Components: Configuration
> Reporter: Sumanth Pasupuleti
> Assignee: Sumanth Pasupuleti
> Priority: Minor
> Fix For: 4.0
>
>
> Ending up with a keyspace of RF=1 is unfortunately pretty easy in C* right
> now - the system_auth table for example is created with RF=1 (to take into
> account single node setups afaict from CASSANDRA-5112), and a user can
> further create a keyspace with RF=1 posing availability and streaming risks
> (e.g. rebuild).
> I propose we add two configuration options in cassandra.yaml:
> # {{default_keyspace_rf}} (default: 1) - If replication factors are not
> specified, use this number.
> # {{required_minimum_keyspace_rf}} (default: unset) - Prevent users from
> creating a keyspace with an RF less than what is configured
> These settings could further be re-used to:
> * Provide defaults for new keyspaces created with SimpleStrategy or
> NetworkTopologyStrategy (CASSANDRA-14303)
> * Make the automatic token allocation algorithm interface more intuitive
> allowing easy use of the new token allocation algorithm.
> At the end of the day, if someone really wants to allow RF=1, they simply
> don’t set the setting. For backwards compatibility the default remains 1 and
> C* would create with RF=1, and would default to current behavior of allowing
> any RF on keyspaces.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
