Details
-
Bug
-
Status: Resolved
-
Low
-
Resolution: Fixed
-
None
-
Degradation
-
Low
-
Low Hanging Fruit
-
User Report
-
All
-
None
-
Description
There are a few problems:
4.0+:
- the virtual table displays only the cassandra.yaml values for both properties, all changes after startup are not updated
4.1+:
- Breaking compatibility - -1 was considered disabled, this should be considered as null now for the new config. The converter should be updated. There is a test for the -1, disable but it didn't caught the issue because of the previous issue mentioned (the disconnect between jmx and the actual property in Config class)
Attachments
Issue Links
- is a child of
-
CASSANDRA-17734 Validate that JMX and the Settings Virtual Table are aligned
- Open