Details
-
Bug
-
Status: Open
-
Normal
-
Resolution: Unresolved
-
None
-
Correctness
-
Normal
-
Low Hanging Fruit
-
User Report
-
All
-
None
-
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.
Attachments
Issue Links
- is related to
-
CASSANDRA-17431 Move the rest of the Config parameters to the new Config framework
- Resolved