[
https://issues.apache.org/jira/browse/CASSANDRA-11303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036619#comment-18036619
]
Michael Semb Wever commented on CASSANDRA-11303:
------------------------------------------------
[~curlylrt], [~clohfink], i'm a bit confused really the last two comments…
from what I can tell the pr (#3683) is the application-level throttling
implementation, and TCP back-pressure is what operators are otherwise DIY
implementing for the clusters today. And that's there's two questions now being
raised: a) how might application-level throttling play with tcp settings, and
b) introducing per-session rate limiter in the application-level
implementation. Have I got that right ? If we are short on time/attention on
this ticket, are there serious concerns identified wrt (a) that are preventing
the PR from being considered as an initial incremental improvement…?
> New inbound throughput parameters for streaming
> -----------------------------------------------
>
> Key: CASSANDRA-11303
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11303
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Local/Config
> Reporter: Satoshi Konno
> Assignee: Runtian Liu
> Priority: Low
> Attachments: 11303_inbound_limit_debug_20160419.log,
> 11303_inbound_nolimit_debug_20160419.log,
> 11303_inbound_patch_for_trunk_20160419.diff,
> 11303_inbound_patch_for_trunk_20160525.diff,
> 11303_inbound_patch_for_trunk_20160704.diff,
> 200vs40inboundstreamthroughput.png, cassandra_inbound_stream.diff
>
>
> Hi,
> To specify stream throughputs of a node more clearly, I would like to add the
> following new inbound parameters like existing outbound parameters in the
> cassandra.yaml.
> - stream_throughput_inbound_megabits_per_sec
> - inter_dc_stream_throughput_outbound_megabits_per_sec
> We use only the existing outbound parameters now, but it is difficult to
> control the total throughputs of a node. In our production network, some
> critical alerts occurs when a node exceed the specified total throughput
> which is the sum of the input and output throughputs.
> In our operation of Cassandra, the alerts occurs during the bootstrap or
> repair processing when a new node is added. In the worst case, we have to
> stop the operation of the exceed node.
> I have attached the patch under consideration. I would like to add a new
> limiter class, StreamInboundRateLimiter, and use the limiter class in
> StreamDeserializer class. I use Row::dataSize( ）to get the input throughput
> in StreamDeserializer::newPartition(), but I am not sure whether the
> dataSize() returns the correct data size.
> Can someone please tell me how to do it ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
