[
https://issues.apache.org/jira/browse/CASSANDRA-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022637#comment-17022637
]
Jordan West commented on CASSANDRA-15519:
-----------------------------------------
[~clohfink] thanks for the input. Could you help me understand a bit better the
value in moving the methods (I can certainly make them more meaningful in
either place)? The reason I ask is because from my (limited) perspective its
pretty much the same difficultly to change the values regardless of the MBean
they live in and discovery is a matter of documentation (which I can add as
part of this patch). I'm open to making the change if your experience tells you
it will be much more valuable – my hesitation is that it exposes either Server
to StorageProxy or visa-versa when currently there is a pretty clean
delineation of layers there.
> 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
