From user-return-19418-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Tue Aug 2 22:18:06 2011 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 95998637E for ; Tue, 2 Aug 2011 22:18:06 +0000 (UTC) Received: (qmail 93085 invoked by uid 500); 2 Aug 2011 22:18:04 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 93033 invoked by uid 500); 2 Aug 2011 22:18:03 -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 93020 invoked by uid 99); 2 Aug 2011 22:18:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2011 22:18:03 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a53.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2011 22:17:56 +0000 Received: from homiemail-a53.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a53.g.dreamhost.com (Postfix) with ESMTP id B394F138058 for ; Tue, 2 Aug 2011 15:17:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=subject :references:from:content-type:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; q=dns; s= thelastpickle.com; b=b4Hcgi1RUYcIGnU5FA4HMFQAj7MGqlhxc/4PxM9GP+g 2tMmONYkbiL4k+eODmwCmrJZL3VJKbA+gh1vTR9ve/15YOmQSK5gXimRUTQGxkJG KAeB4Uo6OI+ui3Xzyk7RXKhK11To/OH83UxdBcPWOC02rfVRpx8kBf8tIDvc1xxM = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h= subject:references:from:content-type:in-reply-to:message-id:date :to:content-transfer-encoding:mime-version; s=thelastpickle.com; bh=ncZCH/t9JF+Eu8m1z2o+hW5239o=; b=ppP7lrD1JImWTT0ooWkSqou4OsS9 5RpFI9lfTQWN77LgoBT9r5wX2W+ug0ix93CoWP7qkwGAMiaSc1stEyWQw35Lza4I AN9+IGhP7WejJ5aREYbdxgHLYRxTNAeH3TWN5MtPzsplUl18TzuXTdEfS1dKvaDz zDInoqUzxOedWoY= Received: from [115.189.20.123] (unknown [115.189.20.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a53.g.dreamhost.com (Postfix) with ESMTPSA id EF047138057 for ; Tue, 2 Aug 2011 15:17:29 -0700 (PDT) Subject: Re: fix for repair causing a node load to double References: From: Aaron Morton Content-Type: multipart/alternative; boundary=Apple-Mail-1--991049060 X-Mailer: iPad Mail (8L1) In-Reply-To: Message-Id: <92EC2618-262F-48BB-8400-BCE26D9E1F2E@thelastpickle.com> Date: Wed, 3 Aug 2011 10:19:53 +1200 To: "user@cassandra.apache.org" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (iPad Mail 8L1) --Apple-Mail-1--991049060 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Try dropping the min compaction threshold via node tool to 2, that should fo= rce every compaction bucket to get processed. Use nodetool flush to trigger minor compaction for all cf's. Clean will only remove load if you have moved tokens. Cheers ----------------- Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 3/08/2011, at 2:13 AM, Adi wrote: > Cassandra 0.7.6 , 4 node cluster=20 >=20 > I ran a nodetool repair for a column family a week ago which caused the lo= ad on that node to double. The diagnosis was that I had hit https://issues.a= pache.org/jira/browse/CASSANDRA-2280 > and that minor compactions will get rid of the unnecessary data and reduce= the load. That node has finished doing a round of Minor compactions over th= e weekend and still the load is 2x of what it is supposed to be.=20 >=20 > Is nodetool cleanup an option to remove the extra data. I am running a cle= anup and it has gone through 50% of the data and retained all of it. >=20 > Any suggestions?=20 >=20 > -Adi >=20 >=20 --Apple-Mail-1--991049060 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Try dropping the min compaction thresho= ld via node tool to 2, that should force every compaction bucket to get proc= essed.

Use nodetool flush to trigger minor compaction for a= ll cf's.

Clean will only remove load if you have mo= ved tokens.

Cheers

-------------= ----
Aaron Morton
Freelance Cassandra Developer
@aaronmorton

On 3/08/2011, at 2:13 AM, Adi <= ;adi.pandit@gmail.com> wrote:=

Cassandra 0.7.6= , 4 node cluster 

I ran a nodetool repair for a co= lumn family a week ago which caused the load on that node to double. The dia= gnosis was that I had hit https://issues.apache.org/jira/browse/CASSANDRA-2280
and that minor compactions will get rid of the unnecessary data and reduce t= he load. That node has finished doing a round of Minor compactions over the w= eekend and still the load is 2x of what it is supposed to be. 

Is nodetool cleanup an option to remove the extra data. I= am running a cleanup and it has gone through 50% of the data and retained a= ll of it.

Any suggestions? 

-Adi


= --Apple-Mail-1--991049060--