[CASSANDRA-17734] Validate that JMX and the Settings Virtual Table are aligned

• Type: Task
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 4.0.x, 4.1.x, 5.x
• Component/s: Local/Config
• Change Category: Operability
• Complexity: Low Hanging Fruit
• Platform: All
• Assignee: Unassigned
• Reporter: Ekaterina Dimitrova
• Created: 06/Jul/22 14:07
• Updated: 07/Mar/23 10:54

Description

I discovered JMX methods that are not updating the Config parameters but directly the usage. (see index_summary_resize_interval) 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 the properties getters&setters&JMX methods and for tickets to fix any discovered bugs.

 

CC [e-mail] and dcapwell 

Issue Links

• is a parent of: CASSANDRA-17736 Settings Virtual Table should display the values assigned to a property in the DatabaseDescriptor on startup and not null (as per the yaml)
• is a parent of: CASSANDRA-17735 Fix issues with index_summary_resize_interval and index_summary_capacity
• is a parent of: CASSANDRA-17737 Validate that JMX updates in Config class any properties that were moved to the new config classes and not local copies
• is a parent of: CASSANDRA-17738 Validate that JMX updates any new 4.1 properties (non-duration, non-data rate, non-data storage) in Config class and not local copies which can lead to inconsistencies between JMX and Settings Virtual Table after startup
• relates to: CASSANDRA-15254 Allow UPDATE on settings virtual table to change running configurations