cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satoshi Konno (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-11303) New inbound throughput parameters for streaming
Date Fri, 04 Mar 2016 04:45:41 GMT
Satoshi Konno created CASSANDRA-11303:

             Summary: New inbound throughput parameters for streaming
                 Key: CASSANDRA-11303
             Project: Cassandra
          Issue Type: New Feature
          Components: Configuration
            Reporter: Satoshi Konno
            Priority: Minor
         Attachments: cassandra_inbound_stream.diff


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