[ 
https://issues.apache.org/jira/browse/CASSANDRA-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023270#comment-17023270
 ] 

Chris Lohfink commented on CASSANDRA-15519:
-------------------------------------------

Just putting like things near each other. Also you are creating a whole new jmx 
domain for a single op and having to manually manage registering and 
unregistering the mbean per ip. This can be done with a couple jmx ops or a 
registered metric and tooling already built wont need to build a custom one off 
just to support this.

> Make native_transport_max_concurrent_requests_in_bytes(_per_ip) changeable at 
> runtime
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-15519
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15519
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Config, Messaging/Client
>            Reporter: Jordan West
>            Assignee: Jordan West
>            Priority: Normal
>              Labels: pull-request-available
>             Fix For: 4.0-beta
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> CASSANDRA-15013 added configurable global and per endpoint limits on the 
> number of in flight requests, measured in bytes. During times when the 
> cluster is overloaded, it can be useful to change this setting without having 
> to restart the Cassandra process. Changing the limits should affect all 
> existing and new connections.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to