cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Miklosovic (Jira)" <>
Subject [jira] [Comment Edited] (CASSANDRA-14557) Consider adding default and required keyspace replication options
Date Wed, 18 Aug 2021 06:59:00 GMT


Stefan Miklosovic edited comment on CASSANDRA-14557 at 8/18/21, 6:58 AM:

That is true but it is still better than restarting them all :) 

This could be some nodetool command or it might be all hidden behind that method, fetching
all topology and so on ... doing this against each node by us, it does not have to be done
_per node_.

was (Author: stefan.miklosovic):
That is true but it is still better than restarting them all :)

> Consider adding default and required keyspace replication options
> -----------------------------------------------------------------
>                 Key: CASSANDRA-14557
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Config
>            Reporter: Sumanth Pasupuleti
>            Assignee: Sumanth Pasupuleti
>            Priority: Low
>              Labels: 4.0-feature-freeze-review-requested
>             Fix For: 4.x
>         Attachments: 14557-4.0.txt, 14557-trunk.patch
> 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
>  * 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message