You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/04/02 01:56:00 UTC

[jira] [Updated] (CASSANDRA-17515) Fix setters for native_transport_max_concurrent_requests_in_bytes and native_transport_max_concurrent_requests_in_bytes_per_ip

     [ https://issues.apache.org/jira/browse/CASSANDRA-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ekaterina Dimitrova updated CASSANDRA-17515:
--------------------------------------------
    Fix Version/s: 3.0.x
                   3.11.x
                   4.0.x

> Fix setters for native_transport_max_concurrent_requests_in_bytes and native_transport_max_concurrent_requests_in_bytes_per_ip 
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17515
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17515
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Config
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> 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 back port that fix.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org