Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 975BB9A1F for ; Tue, 27 Sep 2011 16:02:46 +0000 (UTC) Received: (qmail 69976 invoked by uid 500); 27 Sep 2011 16:02:41 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 69919 invoked by uid 500); 27 Sep 2011 16:02:41 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 69674 invoked by uid 99); 27 Sep 2011 16:02:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Sep 2011 16:02:40 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of scode@scode.org designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Sep 2011 16:02:31 +0000 Received: by wwf22 with SMTP id 22so5743746wwf.25 for ; Tue, 27 Sep 2011 09:02:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.186.146 with SMTP id w18mr9325181wem.29.1317139331304; Tue, 27 Sep 2011 09:02:11 -0700 (PDT) Sender: scode@scode.org Received: by 10.216.82.136 with HTTP; Tue, 27 Sep 2011 09:02:11 -0700 (PDT) X-Originating-IP: [212.181.83.218] In-Reply-To: References: Date: Tue, 27 Sep 2011 18:02:11 +0200 X-Google-Sender-Auth: 9AiLHbXkFf-3wYeczzOQ3dW-nQE Message-ID: Subject: Re: anyway to throttle nodetool repair? From: Peter Schuller To: user@cassandra.apache.org Cc: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org > I saw the ticket about compaction throttling, just wonder is that necessary > to add an option or is there anyway to do repair throttling? > every time I run nodetool repair, it uses all disk io and the server load > goes up quickly, just wonder is there anyway to make it smoother. The validating compaction that is part of repair is subject to compaction throttling. The streaming of sstables afterwards is not however. In 1.0 there is thottling of streaming: https://issues.apache.org/jira/browse/CASSANDRA-3080 -- / Peter Schuller (@scode on twitter)