[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: Status: In Progress (was: Patch Available) > 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 check those setters and probably to back port similar fix. > CC [~maedhroz] , [~dcapwell] and [~mck] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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: Status: Patch Available (was: Review In Progress) > 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 check those setters and probably to back port similar fix. > CC [~maedhroz] , [~dcapwell] and [~mck] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Caleb Rackliffe updated CASSANDRA-17515: Reviewers: Caleb Rackliffe, Caleb Rackliffe Caleb Rackliffe, Caleb Rackliffe (was: Caleb Rackliffe) Status: Review In Progress (was: Patch Available) > 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 check those setters and probably to back port similar fix. > CC [~maedhroz] , [~dcapwell] and [~mck] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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:
Test and Documentation Plan:
{*}{*}The patch is the same for all branches, pushed CI:
[3.0|https://github.com/ekaterinadimitrova2/cassandra/commit/b97b0079137df97c8b2f2094d64ed5e91164fbbb]|[Jenkins
CI |https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1557/]
[3.11|https://github.com/ekaterinadimitrova2/cassandra/commit/a8f64cb5ee8697b811aac01ff46bcce8a00fba0a]|[Jenkins
CI |https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1558/]
[4.0|https://github.com/ekaterinadimitrova2/cassandra/commit/f0ba967e40661892cc58f6796b4c6eb3484c971d]|[Jenkins
CI|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1559/]
Status: Patch Available (was: In Progress)
> 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 check those setters and probably to back port similar fix.
> CC [~maedhroz] , [~dcapwell] and [~mck]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[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: 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] was: 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 that fix. CC [~maedhroz] , [~dcapwell] and [~mck] > 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 check those setters and probably to back port similar fix. > CC [~maedhroz] , [~dcapwell] and [~mck] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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: 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 that fix. CC [~maedhroz] , [~dcapwell] and [~mck] was: 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 that fix. CC [~maedhroz] , [~dcapwell] and [~mck] > 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 check those setters and probably to back port that fix. > CC [~maedhroz] , [~dcapwell] and [~mck] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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: 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 back port that fix. CC [~maedhroz] , [~dcapwell] and [~mck] was: 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. > 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. > > CC [~maedhroz] , [~dcapwell] and [~mck] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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: 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 that fix. CC [~maedhroz] , [~dcapwell] and [~mck] was: 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. CC [~maedhroz] , [~dcapwell] and [~mck] > 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 check those setters and probably to back port that fix. > > CC [~maedhroz] , [~dcapwell] and [~mck] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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: Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Component/s: Local/Config Discovered By: User Report Severity: Normal Assignee: Ekaterina Dimitrova Status: Open (was: Triage Needed) > 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 > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
