[CASSANDRA-17341] Merge guardrails and track warnings configurations

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.x
• Component/s: Feature/Guardrails, Local/Config
• Change Category: Operability
• Complexity: Normal
• Platform: All

Test and Documentation Plan

Testing relies on the current tests for both guardrails and track warnings

• Assignee: Andres de la Peña
• Reporter: Andres de la Peña

Authors

Andres de la Peña

• Created: 02/Feb/22 15:56
• Updated: 22/Mar/23 19:14
• Resolved: 22/Mar/23 19:14

Description

As discussed in CASSANDRA-17148, a first step for the integration between guardrails and track warnings is merging their configurations, which are almost identical. This ticket would cover merging their config sections in cassandra.yaml and their corresponding JMX getters and setters. A tighter integration between the internals of both features wouldn't be part of this ticket, but of either CASSANDRA-17148 or a new subtask of it.

Neither guardrails nor track warnings have included in any release, so it would be desirable to do this before releasing 4.1 so we don't have to deprecate properties.

There's an ongoing discussion about refactoring cassandra.yaml spread across CASSANDRA-17292, CASSANDRA-17188 and CASSANDRA-17212. I understand that any change affecting the config for guardrails also affects the config track warnings, because they are almost identical. Thus, I think that merging both config sections would ease any refactoring plan that is agreed on that discussion.

Issue Links

• duplicates: CASSANDRA-17560 Migrate track_warnings to more standard naming conventions and use latest configuration types rather than long
• is a child of: CASSANDRA-17148 Adapt track_warnings to Guardrails