[CASSANDRA-17160] Emit warnings for deprecated parameters (changed names) only once

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 4.0.2, 4.1-alpha1, 4.1
• Component/s: Build
• Change Category: Operability
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/1a05fcf52b8162cc0ed7c6dbcf6e0109b50fa582

Test and Documentation Plan

4.0 | Jenkins
trunk | Jenkins

• Assignee: Ekaterina Dimitrova Assign to me
• Reporter: Ekaterina Dimitrova

Reviewers

Caleb Rackliffe

• Created: 17/Nov/21 20:12
• Updated: 27/May/22 19:25
• Resolved: 08/Jan/22 20:43

Description

We added backward compatibility for two config parameters in CASSANDRA-17141 to fix a bug but I realized that with the current setup, a warning for deprecated parameter can be logged more than once which is not needed and only introduces noise to the logs. 

I already fixed that in CASSANDRA-15234 where this would lead to a lot of warnings and it is easy to spot. I will backport the tiny fix here too in case we add more parameters, etc; to prevent the potential noise.  

 

Issue Links

• relates to: CASSANDRA-15234 Standardise config and JVM parameters
• relates to: CASSANDRA-17141 internode_send_buff_size_in_bytes and internode_recv_buff_size_in_bytes from cassandra.yaml