The artifacts for this vote happen to have https://issues.apache.org/jira/browse/CASSANDRA-3343.
This is a purely cosmetic issue, and clearly I don't want to reroll the vote for this, which would delay the release. But I also think that fixing this issue has zero chance of screwing anything up, so while it feels stupid to delay the release for that, it also feels stupid to me to annoy people with it. So I have created new artifacts, based on the previous ones but with the infamous 'echo $CLASSPATH' removed from cassandra.in.sh. And what I'm proposing is to simply switch to those last artifacts for the release instead of the initial ones, but without restarting a vote just for that. The new artifacts are: SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r1181741 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-053/org/apache/cassandra/apache-cassandra/1.0.0/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-053/ I've also put them and the corresponding debian package at http://people.apache.org/~slebresne/with_3343/ We still have 2 days to go on this vote, so this is not a sneaky move either. However, I've kept the initial artifacts around for now, so if someone disagree strongly, we'll stick to the initial artifacts. -- Sylvain On Tue, Oct 11, 2011 at 7:30 AM, Todd Burruss <bburr...@expedia.com> wrote: > This is a bit preliminary, but wanted to get this to you guys knowing the > vote is in progress .... > > using these artifacts I am seeing the following exception on restart. > (also with RC1 and RC2.) the only interesting tidbit is that it seems to > only happen when writing via direct calls to StorageProxy. I can't quite > compare apples to apples, but if I only write via Thrift interface, replay > of the commitlog works. Write via StorageProxy (but a different CF than > via Thrift) the replay throws exception. > > > > INFO 22:06:50,671 Replaying > /var/lib/cassandra/commitlog/CommitLog-1318309128835.log, > /var/lib/cassandra/commitlog/CommitLog-1318309569302.log > INFO 22:06:50,700 Finished reading > /var/lib/cassandra/commitlog/CommitLog-1318309128835.log > ERROR 22:06:50,702 Exception encountered during startup > org.apache.cassandra.db.ColumnSerializer$CorruptColumnException: invalid > column name length 0 > at > org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.java: > 89) > at > org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.java: > 36) > at > org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnFam > ilySerializer.java:143) > at > org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnFam > ilySerializer.java:135) > at > org.apache.cassandra.db.ColumnFamilySerializer.deserialize(ColumnFamilySeri > alizer.java:128) > at > org.apache.cassandra.db.RowMutation$RowMutationSerializer.deserialize(RowMu > tation.java:404) > at > org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:284) > at > org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:171) > at > org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandr > aDaemon.java:196) > at > org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassa > ndraDaemon.java:337) > at > org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:106) > org.apache.cassandra.db.ColumnSerializer$CorruptColumnException: invalid > column name length 0 > at > org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.java: > 89) > at > org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.java: > 36) > at > org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnFam > ilySerializer.java:143) > at > org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnFam > ilySerializer.java:135) > at > org.apache.cassandra.db.ColumnFamilySerializer.deserialize(ColumnFamilySeri > alizer.java:128) > at > org.apache.cassandra.db.RowMutation$RowMutationSerializer.deserialize(RowMu > tation.java:404) > at > org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:284) > at > org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:171) > at > org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandr > aDaemon.java:196) > at > org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassa > ndraDaemon.java:337) > at > org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:106) > Exception encountered during startup: invalid column name length 0 > > > > > On 10/10/11 9:24 AM, "Sylvain Lebresne" <sylv...@datastax.com> wrote: > >>As said while closing previous vote, CASSANDRA-3338 felt important enough >>to >>warrant a reroll. So here it is: I propose the following artifacts for >>release >>as 1.0.0 (those are the same as the previous + the patch for >>CASSANDRA-3338 >>and a one line fix to the build file so that it picks the right version of >>snappy-java from maven central). >> >>SVN: >>https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r11809 >>70 >>Artifacts: >>https://repository.apache.org/content/repositories/orgapachecassandra-046/ >>org/apache/cassandra/apache-cassandra/1.0.0/ >>Staging repository: >>https://repository.apache.org/content/repositories/orgapachecassandra-046/ >> >>The artifacts as well as the debian package are also available here: >>http://people.apache.org/~slebresne/ >> >>The vote will be open for 72 hours (longer if needed). >> >>[1]: http://goo.gl/JB2NL (CHANGES.txt) >>[2]: http://goo.gl/x6gTC (NEWS.txt) > >
