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.
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 <firstname.lastname@example.org> wrote:
> 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?
> Jake Maizel
> Head of Network Operations
> Mail & GTalk: email@example.com
> Skype: jakecloud
> Rosenthaler strasse 13, 101 19, Berlin, DE
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support