Re: Recompacting all sstables

Hi, On 11/01/2013 09:15 PM, Robert Coli wrote: > On Fri, Nov 1, 2013 at 12:47 PM, Jiri Horky > wrote: > > since we upgraded half of our Cassandra cluster to 2.0.0 and we > use LCS, > we hit CASSANDRA-6284 bug. > > > 1) Why upgrade a cluster to 2.0.0? Hopefully

Re: Recompacting all sstables

On Fri, Nov 1, 2013 at 12:47 PM, Jiri Horky wrote: > since we upgraded half of our Cassandra cluster to 2.0.0 and we use LCS, > we hit CASSANDRA-6284 bug. 1) Why upgrade a cluster to 2.0.0? Hopefully not a production cluster? [1] 2) CASSANDRA-6284 is ouch, thx for filing and patching! 3) What

Recompacting all sstables

Hi all since we upgraded half of our Cassandra cluster to 2.0.0 and we use LCS, we hit CASSANDRA-6284 bug. So basically all data in sstables created after the upgrade are wrongly (non-uniformly within compaction levels) distributed. This causes a huge overhead when compacting new sstables (see the