[ 
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789634#comment-17789634
 ] 

Stefan Miklosovic commented on CASSANDRA-15254:
-----------------------------------------------

I just stumbled upon this again ... (which tells me there is something 
attractive in this ticket that I tend to gravitate towards it every now and 
then :) )

Imagine a scenario that we start a node with default configuration from 
cassandra.yaml and then somebody tweaks the configuration via a system table so 
it starts to diverge from what is in cassandra.yaml on the disk. When that node 
is restarted, since all settings we changed were living solely in a memory, we 
lost that configuration, right? So you have to go to that node again, start it 
and manually tweak it again (an operator might not even know anymore what the 
tweaks were about).

What would be great is to have some nodetool command which would connect to a 
running node and it would dump what is in DatabaseDescriptor into a yaml file. 
Then, this file might be used upon node's restart. 

> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to