Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 61209 invoked from network); 25 Feb 2011 14:53:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Feb 2011 14:53:50 -0000 Received: (qmail 34671 invoked by uid 500); 25 Feb 2011 14:53:48 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 34466 invoked by uid 500); 25 Feb 2011 14:53:45 -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 34458 invoked by uid 99); 25 Feb 2011 14:53:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 14:53:43 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [85.158.136.3] (HELO mail123.messagelabs.com) (85.158.136.3) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 14:53:35 +0000 X-VirusChecked: Checked X-Env-Sender: daniel.josefsson@shazamteam.com X-Msg-Ref: server-8.tower-123.messagelabs.com!1298645594!20427548!1 X-StarScan-Version: 6.2.9; banners=shazamteam.com,-,- X-Originating-IP: [217.28.130.38] Received: (qmail 23736 invoked from network); 25 Feb 2011 14:53:14 -0000 Received: from hostedexchange.hostedservice.com (HELO outlook.hostedservice2.net) (217.28.130.38) by server-8.tower-123.messagelabs.com with RC4-SHA encrypted SMTP; 25 Feb 2011 14:53:14 -0000 Received: from [192.168.195.7] (217.111.143.154) by smtp.hostedservice2.net (192.168.16.122) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 25 Feb 2011 14:53:14 +0000 Subject: Re: Running multiple compactions concurrently From: Daniel Josefsson To: "user@cassandra.apache.org" In-Reply-To: References: Content-Type: multipart/alternative; boundary="=-Vpirzmp8IAkRlK78v+3z" Date: Fri, 25 Feb 2011 14:53:13 +0000 Message-ID: <1298645593.2183.6.camel@danielj-OptiPlex-780> MIME-Version: 1.0 X-Mailer: Evolution 2.30.3 X-Virus-Checked: Checked by ClamAV on apache.org --=-Vpirzmp8IAkRlK78v+3z Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit The compaction will be part of a Cassandra upgrade (where all nodes will have to be taken down), so no clients will be hitting it until the upgrade is complete. I just want to minimize the downtime. Thanks, this is basically what I wanted to hear. Daniel On Fri, 2011-02-25 at 13:24 +0000, Gary Dusbabek wrote: > If your cluster has the overall IO capacity to perform a simultaneous > compaction on every node and still adequately service reads and > writes, then yes. If you're concerned about availability, your best > bet will be to stagger the compactions. > > Gary. > > > On Fri, Feb 25, 2011 at 04:24, Daniel Josefsson wrote: > > We experienced the java.lang.NegativeArraySizeException when upgrading to > > 0.7.2 in staging. The proposed solution (running compaction) seems to have > > solved this. However it took a lot of time to run. > > > > Is it safe to invoke a major compaction on all of the machines concurrently? > > > > I can't see a reason why it wouldn't, but I want to be sure :) > > > > Thanks, > > Daniel > > > > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ -- Daniel Josefsson Software Engineer Shazam Entertainment Ltd 26-28 Hammersmith Grove, London W6 7HA w: www.shazam.com Please consider the environment before printing this document This e-mail and its contents are strictly private and confidential. It must not be disclosed, distributed or copied without our prior consent. If you have received this transmission in error, please notify Shazam Entertainment immediately on: +44 (0) 020 8742 6820 and then delete it from your system. Please note that the information contained herein shall additionally constitute Confidential Information for the purposes of any NDA between the recipient/s and Shazam Entertainment. Shazam Entertainment Limited is incorporated in England and Wales under company number 3998831 and its registered office is at 26-28 Hammersmith Grove, London W6 7HA. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ --=-Vpirzmp8IAkRlK78v+3z Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit The compaction will be part of a Cassandra upgrade (where all nodes will have to be taken down), so no clients will be hitting it until the upgrade is complete. I just want to minimize the downtime.

Thanks, this is basically what I wanted to hear.

Daniel

On Fri, 2011-02-25 at 13:24 +0000, Gary Dusbabek wrote:
If your cluster has the overall IO capacity to perform a simultaneous
compaction on every node and still adequately service reads and
writes, then yes.  If you're concerned about availability, your best
bet will be to stagger the compactions.

Gary.


On Fri, Feb 25, 2011 at 04:24, Daniel Josefsson <jideji@gmail.com> wrote:
> We experienced the java.lang.NegativeArraySizeException when upgrading to
> 0.7.2 in staging. The proposed solution (running compaction) seems to have
> solved this. However it took a lot of time to run.
>
> Is it safe to invoke a major compaction on all of the machines concurrently?
>
> I can't see a reason why it wouldn't, but I want to be sure :)
>
> Thanks,
> Daniel
>
>

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

--


Daniel Josefsson

Software Engineer

Shazam Entertainment Ltd    
26-28 Hammersmith Grove, London W6 7HA
w:         www.shazam.com

Please consider the environment before printing this document

This e-mail and its contents are strictly private and confidential. It must not be disclosed, distributed or copied without our prior consent. If you have received this transmission in error, please notify Shazam Entertainment immediately on: +44 (0) 020 8742 6820 and then delete it from your system. Please note that the information contained herein shall additionally constitute Confidential Information for the purposes of any NDA between the recipient/s and Shazam Entertainment. Shazam Entertainment Limited is incorporated in England and Wales under company number 3998831 and its registered office is at 26-28 Hammersmith Grove, London W6 7HA. 



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--=-Vpirzmp8IAkRlK78v+3z--