Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 43189197EB for ; Tue, 19 Apr 2016 06:16:26 +0000 (UTC) Received: (qmail 93551 invoked by uid 500); 19 Apr 2016 06:16:26 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 93353 invoked by uid 500); 19 Apr 2016 06:16:25 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 93300 invoked by uid 99); 19 Apr 2016 06:16:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2016 06:16:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 89F8D2C1F61 for ; Tue, 19 Apr 2016 06:16:25 +0000 (UTC) Date: Tue, 19 Apr 2016 06:16:25 +0000 (UTC) From: "Satoshi Konno (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-11303) New inbound throughput parameters for streaming MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-11303?page=3Dcom.atl= assian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satoshi Konno updated CASSANDRA-11303: -------------------------------------- Attachment: 11303_inbound_nolimit_debug_20160419.log 11303_inbound_limit_debug_20160419.log > New inbound throughput parameters for streaming > ----------------------------------------------- > > Key: CASSANDRA-11303 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1130= 3 > Project: Cassandra > Issue Type: New Feature > Components: Configuration > Reporter: Satoshi Konno > Priority: Minor > Attachments: 11303_inbound_limit_debug_20160419.log, 11303_inboun= d_nolimit_debug_20160419.log, 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 =20 > We use only the existing outbound parameters now, but it is difficult to = control the total throughputs of a node.=E3=80=80In our production network,= some critical alerts occurs when a node exceed the specified total through= put 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 s= top 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 Strea= mDeserializer class. I use Row::dataSize( =EF=BC=89to get the input through= put in StreamDeserializer::newPartition(), but I am not sure whether the da= taSize() returns the correct data size. > Can someone please tell me how to do it ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)