Unfortunately no. Second time I did the test:
Restore 4 nodes to a new Cassandra cluster (0.7.8) Upgrade to 1.0.0 Run nodetool scrub on each node after upgrade before upgrading next node. Upgrade to 1.0.3 Upgrade to 1.0.5 Run nodetool repair on all nodes. All process was successful. What does this error means and how is it affecting my cluster? Do you think it is safe to upgrade to 1.0.5 and disregard this error? Thanks Michael -----Original Message----- From: Jonathan Ellis [mailto:jbel...@gmail.com] Sent: Thursday, December 01, 2011 2:10 AM To: user@cassandra.apache.org Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released I don't think so. That code hasn't changed in a long time. Is it reproducible? On Wed, Nov 30, 2011 at 2:46 PM, Michael Vaknine <micha...@citypath.com> wrote: > Hi, > Upgrade 1.0.3 to 1.0.5 > I have this errors > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 > AbstractCassandraDaemon.java (line 133) Fatal exception in thread Thread > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 java.lang.AssertionError > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.db.ColumnFamilyStore.maybeSwitchMemtable(ColumnFamilySt > ore.java:671) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java: > 745) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.db.ColumnFamilyStore.forceBlockingFlush(ColumnFamilySto > re.java:750) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.db.index.keys.KeysIndex.forceBlockingFlush(KeysIndex.ja > va:119) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.db.index.SecondaryIndexManager.flushIndexesBlocking(Sec > ondaryIndexManager.java:258) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.db.index.SecondaryIndexManager.maybeBuildSecondaryIndex > es(SecondaryIndexManager.java:123) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSessi > on.java:151) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReade > r.java:103) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection. > java:184) > TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at > org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.jav > a:81) > > Is this another regression? > > Thanks > Michael > > -----Original Message----- > From: Brandon Williams [mailto:dri...@gmail.com] > Sent: Wednesday, November 30, 2011 9:43 PM > To: user@cassandra.apache.org > Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released > > On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <micha...@citypath.com> > wrote: >> The files are not on the site >> The requested URL > /apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz >> was not found on this server. > > It takes the mirrors some time to sync. > > -Brandon > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
