Upgrading to 1.0

[Jake Maizel <ja...@soundcloud.com>]

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

Re: Upgrading to 1.0

[Brandon Williams <dr...@gmail.com>]

On Sat, Nov 5, 2011 at 1:31 PM, Jake Maizel <ja...@soundcloud.com> wrote:
> 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.

Any newly written sstable (from a memtable flush, compaction, etc)
will have compression enabled.  Since you'll need to scrub after
upgrading for streaming to work, this will result in all the sstables
being compressed.

-Brandon

Re: Upgrading to 1.0

[Jake Maizel <ja...@soundcloud.com>]

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 <jb...@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 <ja...@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

Re: Upgrading to 1.0

[Jonathan Ellis <jb...@gmail.com>]

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

Re: Upgrading to 1.0

[Zhu Han <sc...@gmail.com>]

I'd like to know whether it is possible to upgrade from 0.6.13 to 1.0.x
directly, either.

Is there anything we should notice that "nodetool scrub" might not fix?


On Wed, Nov 2, 2011 at 7:46 PM, Jake Maizel <ja...@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
>