[CASSANDRA-17515] Fix setters for native_transport_max_concurrent_requests_in_bytes and native_transport_max_concurrent_requests_in_bytes_per_ip

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 3.0.x, 3.11.x, 4.0.x
• Component/s: Local/Config
• Bug Category: Correctness
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All

Test and Documentation Plan

{}The patch is the same for all branches, pushed CI:

3.0|Jenkins CI

3.11|Jenkins CI

4.0|Jenkins CI

• Assignee: Unassigned
• Reporter: Ekaterina Dimitrova

Reviewers

Caleb Rackliffe

• Created: 02/Apr/22 01:54
• Updated: 06/Oct/22 19:53

Description

While working on CASSANDRA-17341 we noticed that while native_transport_max_concurrent_requests_in_bytes and native_transport_max_concurrent_requests_in_bytes_per_ip  are checked for -1 during startup and have default value, this is not the case in their setters. 

We fixed this for trunk but those properties exist also in previous versions. We need to check those setters and probably to back port similar fix.

CC maedhroz , dcapwell  and mck 

Issue Links

• is related to: CASSANDRA-17431 Move the rest of the Config parameters to the new Config framework