[
https://issues.apache.org/jira/browse/CASSANDRA-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519435#comment-17519435
]
Stefan Miklosovic edited comment on CASSANDRA-17500 at 4/8/22 8:56 AM:
-----------------------------------------------------------------------
this somehow duplicates efforts in
https://issues.apache.org/jira/browse/CASSANDRA-14557
Ideally, we should make one more guardrail for having minimum RF and I would
remove what was done in 14557 (or at least deprecate it). I think we can remove
it altogether as 4.1 is not released yet and it was added this release cycle. I
dont see any reason why we should have minimum for RF done by one approach and
maximum by Guardrail.
was (Author: smiklosovic):
this somehow duplicates efforts in
https://issues.apache.org/jira/browse/CASSANDRA-14557
Ideally, we should make one more guardrail for having minimum RF and I would
remove what was done in 14557 (or at least deprecate it).
> Create Maximum Data Center 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.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
