[
https://issues.apache.org/jira/browse/CASSANDRA-19593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848590#comment-17848590
]
Stefan Miklosovic commented on CASSANDRA-19593:
-----------------------------------------------
There is minimumReplicationFactor guardrail which looks into
DatabaseDescriptor.getDefaultKeyspaceRF() when validating the value:
{code:java}
public static void validateMinRFThreshold(int warn, int fail)
{
validateMinIntThreshold(warn, fail, "minimum_replication_factor");
if (fail > DatabaseDescriptor.getDefaultKeyspaceRF())
throw new
IllegalArgumentException(format("minimum_replication_factor_fail_threshold to
be set (%d) " +
"cannot be greater than
default_keyspace_rf (%d)",
fail,
DatabaseDescriptor.getDefaultKeyspaceRF()));
} {code}
this is similarly done for maximum_replication_factor.
Obviously, conf.default_keyspace_rf can be different per node, if
misconfigured, so transformation application would not be the same on all nodes
and it might fail on some and not fail on others.
This brings us to more general problem of transactional configuration which
should be done as well. It is questionable if it is desirable to do it as part
of this ticket or not, however, I would like to look into how we could do that
as well.
> Transactional Guardrails
> ------------------------
>
> Key: CASSANDRA-19593
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19593
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails, Transactional Cluster Metadata
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I think it is time to start to think about this more seriously. TCM is
> getting into pretty nice shape and we might start to investigate how to do
> this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
