Hi Tyler, thanks fort that hint. I think we may postpone the C* upgrade for now and will give it another try with a higher version. There is no pressure on that.
Regards Andi From: Tyler Hobbs [mailto:ty...@datastax.com] Sent: Thursday, November 20, 2014 6:09 PM To: user@cassandra.apache.org Subject: Re: Upgrade: C* 2.0.8 -> C* 2.1.1 - Ten thousands of sstable files This could be due to https://issues.apache.org/jira/browse/CASSANDRA-8239, which is fixed in 2.1.2. However, it sounds like the SSTables were present immediately after upgrading, which would rule that out. On Thu, Nov 20, 2014 at 10:25 AM, Andreas Finke <andreas.fi...@solvians.com<mailto:andreas.fi...@solvians.com>> wrote: Hi Robert, thanks for your fast reply. Luckily this was a upgrade in QA environment ;) We are running SizeTierCompaction. I wonder whether all those files were created during running sstables command. Unfortunately we didn’t check at that time. I will try to reproduce again and if this is the case open an issue. However thanks for the link. This is really useful. Thanks! Andi From: Robert Coli [mailto:rc...@eventbrite.com<mailto:rc...@eventbrite.com>] Sent: Thursday, November 20, 2014 5:14 PM To: user@cassandra.apache.org<mailto:user@cassandra.apache.org> Subject: Re: Upgrade: C* 2.0.8 -> C* 2.1.1 - Ten thousands of sstable files On Thu, Nov 20, 2014 at 7:00 AM, Andreas Finke <andreas.fi...@solvians.com<mailto:andreas.fi...@solvians.com>> wrote: we upgraded a 6 node Cluster from Cassandra 2.0.7 to 2.1.1 recently sticking to this guide After upgrade cluster was less responsive than before. One node did not came up at all. For the record : https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/ =Rob -- Tyler Hobbs DataStax<http://datastax.com/>
