[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789650#comment-17789650
]
Stefan Miklosovic commented on CASSANDRA-15254:
-----------------------------------------------
I think what would be super cool to see is the integration with TCM. If we have
a cluster of 30 nodes and you do the tweaking, you need to do this, most
probably, cluster-wide, to see some effects of that in runtime in some
dashboard (latencies, throughput ...) There is also not too much of a reason to
tweak one node in some way and keep the rest untweaked.
If this was integrated with TCM, it would not be a schema change, it would be
transactional configuration change. So by one insert into a cql table, it would
be suddenly visible in all nodes.
Virtual tables which are backed by TCM should not be too hard to implement,
definitely some serious design should go into it but it should be doable.
When Cassandra is started, it would read yaml then it would boot and at the end
of the booting process it would set its config from TCM.
> 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]
