[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789655#comment-17789655
]
Maxim Muzafarov commented on CASSANDRA-15254:
---------------------------------------------
[~smiklosovic] You've raised a good question, but it seems to me that the image
you have of this issue is a bit aside from the whole concept of what we're
trying to improve here. Let me clarify.
We have a cassandra.yaml configuration on disk that is loaded into the runtime
node configuration during node startup, represented as a Config. The
SettingsVirtualTable is a local view of that Config, and I'm pretty sure that
virtual tables will remain local to a node even after TCM. So what we have on
disk and what we have at runtime is slightly different because we are able to
change some of the properties via JMX e.g. compaction throughput. I'm pretty
sure that those sorts of parameters remain local regardless of the existence of
the TCM.
So, as I understand your concerns you want to dump the runtime configuration
into a yaml file, and that makes perfect sense to me.
Here are the issues that should address these concerns:
https://issues.apache.org/jira/browse/CASSANDRA-16513
https://issues.apache.org/jira/browse/CASSANDRA-15989
Let's look at the current issue from the perspective I mentioned above. The
goal is not to provide settings management for ALL node settings, but to make
all settings that can already be managed with JMX available to change via the
SettingsVirtualTable. This is why we have to introduce the @Mutable annotation
in these changes. So it looks to me like your valid concern is not related to
these changes. In short, the goal is to provide another API for local settings
management, so that users can decide which option they prefer JMX or CQL.
> Allow UPDATE on settings virtual table to change running configurations
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-15254
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15254
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Virtual Tables
> Reporter: Chris Lohfink
> Assignee: Maxim Muzafarov
> Priority: Normal
> Fix For: 5.x
>
> Attachments: Configuration Registry Diagram.png
>
> Time Spent: 20h 10m
> Remaining Estimate: 0h
>
> Allow using UPDATE on the system_views.settings virtual table to update
> configs at runtime for the equivalent of the dispersed JMX
> attributes/operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
