There is (1) which attempts to add guardrails get/set configuration to nodetool.
When first encountered, I suggested that we might do a CQL vtable approach instead. This is still not done and Paulo asked if the nodetool approach could not be still added to 5.0 (2) The justification is that we have just GuardrailsMBean with management methods one can call but there is no user-facing tooling around this which would invoke them. An argument can be made that requiring an operator to manually invoke these methods is hardly user-friendly and it would be welcomed if we added get/set guardrails commands to nodetool directly. I was on a fence when I saw we are trying to add nodetool commands to 5.0 / 4.1 while the "end goal" is to have it on CQL but the feedback given from Brandon (3) / Maxwell is that they would still welcome nodetool approach and CQL might be reserved for trunk. Is it OK for the community if we added nodetool get/set guardrailsconfig commands to 4.1, 5.0 and trunk? Then, under (4), the CQL approach would be delivered as well. While adding something quite late to 4.1 / 5.0 when it comes to (technically) an improvement is rather special and should be done exceptionally, we think it still makes sense, especially when it makes the lives of operators simpler in this regard. I do not think that additions like this should not happen when they are contributing to overall betterment of user experience for the whole feature (guardrails) and they are clear additions not touching internal server code as such. The only way a user can toggle guardrails in runtime is via manual invocation of MBean methods and there is no real reason we should not enrich Cassandra with tooling calling it for the reasons explained earlier. Regards (1) https://issues.apache.org/jira/browse/CASSANDRA-19552 (2) https://issues.apache.org/jira/browse/CASSANDRA-19552?focusedCommentId=18003580&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-18003580 (3) https://issues.apache.org/jira/browse/CASSANDRA-19552?focusedCommentId=18004163&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-18004163 (4) https://issues.apache.org/jira/browse/CASSANDRA-19553
