Running multiple compactions concurrently

[Daniel Josefsson <ji...@gmail.com>]

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

Re: Running multiple compactions concurrently

[Daniel Josefsson <da...@shazamteam.com>]

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 <ji...@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 
______________________________________________________________________

Re: Running multiple compactions concurrently

[Gary Dusbabek <gd...@gmail.com>]

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 <ji...@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
>
>