[
https://issues.apache.org/jira/browse/CASSANDRA-19552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003691#comment-18003691
]
Stefan Miklosovic commented on CASSANDRA-19552:
-----------------------------------------------
They can indeed set it via MBean. Not sure what you mean by your last sentence.
I do not think we should ship it in 5.0. We should rather spend time on
delivering it in trunk. What you would end up with is nodetool approach in 5.0
and then in trunk we would most probably do something like CASSANDRA-19593 .
The we would have two solutions in place. How are we going to consolidate that?
This would bring just chaos to trunk and to end user having to manage two
interfaces at once.
> Nodetool to get/set guardrails configurations
> ---------------------------------------------
>
> Key: CASSANDRA-19552
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19552
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/Guardrails
> Reporter: Yuqi Yan
> Assignee: Yuqi Yan
> Priority: Normal
> Fix For: 4.1.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently guardrails are only configurable through JMX / cassandra.yaml
> This provides a nodetool command to interact with all the getters/setters for
> guardrails.
>
> 4.1 PR: [https://github.com/apache/cassandra/pull/3243]
> trunk PR: [https://github.com/apache/cassandra/pull/3244]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
