[
https://issues.apache.org/jira/browse/CASSANDRA-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525913#comment-17525913
]
Andres de la Peña commented on CASSANDRA-17500:
-----------------------------------------------
[~savni_nagarkar] [~dcapwell] regarding passing the client state, I guess we
could do something more or less [like
this|https://github.com/adelapena/cassandra/commit/d1bddfa54cf430b4f836bcdcdbd5e4b3e9b33b4e],
trying to keep the compatibility of 3rd party implementations of
{{AbstractReplicationStrategy}}, if any.
Nevertheless, I think we should start by migrating the min RF to guardrails
(CASSANDRA-17212) before adding the max RF, so we don't have two separate
approaches and config formats for min and max. Also, {{minimum_keyspace_rf}} is
only on trunk, so if we are going to migrate it to guardrails it would be ideal
to do it as soon as possible so we don't have to deprecate it later. wdyt?
> Create Maximum Keyspace Replication Factor Guardrail
> -----------------------------------------------------
>
> Key: CASSANDRA-17500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17500
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Guardrails
> Reporter: Savni Nagarkar
> Assignee: Savni Nagarkar
> Priority: Normal
> Fix For: 4.x
>
>
> This ticket adds a maximum replication factor guardrail to ensure safety when
> creating or altering key spaces. The replication factor will be applied per
> data center. The ticket was prompted as a user set the replication factor
> equal to the number of nodes in the cluster. The property will be added to
> guardrails to ensure consistency.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
