[
https://issues.apache.org/jira/browse/CASSANDRA-17734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17734:
--------------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Component/s: Local/Config
Status: Open (was: Triage Needed)
> Validate that JMX and the Settings Virtual Table are aligned
> ------------------------------------------------------------
>
> Key: CASSANDRA-17734
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17734
> Project: Cassandra
> Issue Type: Task
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Priority: Normal
>
> I discovered JMX methods that are not updating the Config parameters but
> directly the usage. This is a bug in 4.0+ as users will see wrong values in
> the Settings virtual table which rely on the Config parameters if some value
> was changed after startup. It will be explicitly important to ensure there is
> no disconnect between those when we add update option for the Virtual Table
> This ticket is meant to serve as an umbrella for subtasks to check different
> properties and bug tickets for fixes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
