Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Sep 2013 19:55:03 +0000 (UTC)
From: "Nick Bailey (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12610137.1349297600243.4658.1379966103234@arcas>
In-Reply-To: <JIRA.12610137.1349297600243@arcas>
References: <JIRA.12610137.1349297600243@arcas>
Subject: [jira] [Commented] (CASSANDRA-4758) Allow throttling bulk load
 separately from streaming
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775607#comment-13775607 ] 

Nick Bailey commented on CASSANDRA-4758:
----------------------------------------

Prevent long running bulk load operations from affecting bootstrap/move/decom/repair?

Perhaps in that case "don't use the jmx call" is appropriate.
                
> Allow throttling bulk load separately from streaming
> ----------------------------------------------------
>
>                 Key: CASSANDRA-4758
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4758
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Nick Bailey
>              Labels: ponies
>
> Currently when you call the bulkload jmx call, the only way to achieve throttling is by tuning the streaming throttle in general, which affects all streaming operations.
> It would be nice to be able to throttle bulk loading separately.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira