Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 209.85.215.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANpsMSHqmupnvjSz5mnVbp+7YbF866-=t--aFL6F+ANkd6P+Og@mail.gmail.com>
References: <E93AB623-CDB4-4E8B-A4D0-1F5A58A5B690@rhapsody.com>
 <CANpsMSHqmupnvjSz5mnVbp+7YbF866-=t--aFL6F+ANkd6P+Og@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Mon, 22 Aug 2011 10:09:58 -0500
Message-ID: 
 <CALdd-zjtwyRHsV4yLgcb_JMY54Be4GpSu7KTC0v1cjqFNyCGkw@mail.gmail.com>
Subject: Re: Avoid Simultaneous Minor Compactions?
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Specifically, look at compaction_throughput_mb_per_sec in cassandra.yaml

On Mon, Aug 22, 2011 at 12:39 AM, Ryan King <ryan@twitter.com> wrote:
> You should throttle your compactions to a sustainable level.
>
> -ryan
>
> On Sun, Aug 21, 2011 at 10:22 PM, Hefeng Yuan <hfyuan@rhapsody.com> wrote:
>> We just noticed that at one time, 4 nodes were doing minor compaction together, each of them took 20~60 minutes.
>> We're on 0.8.1, 6 nodes, RF5.
>> This simultaneous compactions slowed down the whole cluster, we have local_quorum consistency level, therefore, dynamic_snitch is not helping us.
>>
>> Aside from lower down the compaction thread priority, is there any other way to tell the cluster hold on doing this if other nodes are already compacting?
>>
>> Thanks,
>> Hefeng
>


-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com