cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jake Maizel <j...@soundcloud.com>
Subject Re: Upgrading to 1.0
Date Sat, 05 Nov 2011 18:31:55 GMT
If we upgrade and want to use compression, how is the old data handled?
Does it read and then write all sstables out to new compressed files one at
a time or do something else?  I'm considering the storage require on top of
what is needed for the existing data.

Regards,

jake

On Wed, Nov 2, 2011 at 2:57 PM, Jonathan Ellis <jbellis@gmail.com> wrote:

> 1.0 can read 0.6 data files but is not network-compatible, so you need
> to do an all-at-once upgrade.  Additionally, the Thrift api changed
> started with 0.7; see NEWS.txt for details.
>
> On Wed, Nov 2, 2011 at 6:46 AM, Jake Maizel <jake@soundcloud.com> wrote:
> > Hello,
> > We run a medium sized cluster of 12 nodes on 0.6.13 and would like to
> move
> > to 1.0.  What's the best practices for this?  Can we do a rolling
> upgrade or
> > does the entire cluster need to be upgraded at once?
> > Regards,
> > Jake
> >
> > --
> > Jake Maizel
> > Head of Network Operations
> > Soundcloud
> >
> > Mail & GTalk: jake@soundcloud.com
> > Skype: jakecloud
> >
> > Rosenthaler strasse 13, 101 19, Berlin, DE
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>



-- 
Jake Maizel
Head of Network Operations
Soundcloud

Mail & GTalk: jake@soundcloud.com
Skype: jakecloud

Rosenthaler strasse 13, 101 19, Berlin, DE

Mime
View raw message