cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11303) New inbound throughput parameters for streaming
Date Thu, 16 Feb 2017 23:28:42 GMT


Jason Brown commented on CASSANDRA-11303:

OK, read through the patch and I understand what's going on here. In my current work for CASSANDRA-12229
(which I'm trying to post ASAP), I'm taking into account *some* degree of inbound throughput
management for streaming (I'm using netty High/Low water marks and disabling auto-read). I
haven't accounted for things at a global level, but that's a task specific to that ticket.

Nevertheless, I will make sure to think again about the inbound throughout limits again as
I finish up CASSANDRA-12229.

> New inbound throughput parameters for streaming
> -----------------------------------------------
>                 Key: CASSANDRA-11303
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Configuration
>            Reporter: Satoshi Konno
>            Assignee: Satoshi Konno
>            Priority: Minor
>         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

View raw message