On Sat, Nov 5, 2011 at 1:31 PM, Jake Maizel 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
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
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 wrote:
> Hello,
> We run a medium sized cluster of 12 nodes on 0.6.13
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 wrote:
> Hello,
>
> We run a medium sized cluster of 12 nodes on 0.6.13 and would like t
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:
