cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11303) New inbound throughput parameters for streaming
Date Wed, 15 Feb 2017 13:10:41 GMT


Paulo Motta commented on CASSANDRA-11303:

This review has felt badly through the cracks (I'm really sorry about that), and now 3.X line
is over for improvements, so I'm afraid we will only be able to support this on 4.0 where
we will have an updated NIO streaming protocol. Based on this, I'd like to check with [~jasobrown]
if he already thought through this and/or if this is something that can be easily supported
in a post-CASSANDRA-12229 world.

> 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