You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Sylvain Lebresne <sy...@datastax.com> on 2011/10/10 18:24:43 UTC

[VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

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@r1180970
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)

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Jake Luciani <ja...@gmail.com>.
+1

On Mon, Oct 10, 2011 at 12:24 PM, Sylvain Lebresne <sy...@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@r1180970
> 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)
>



-- 
http://twitter.com/tjake

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Eric Evans <ee...@acunu.com>.
On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne <sy...@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@r1180970
> 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

-- 
Eric Evans
Acunu | http://www.acunu.com | @acunu

Re: [VOTE CLOSE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Sylvain Lebresne <sy...@datastax.com>.
Alright, that sucks. But with 3338, 3346 and 3345 (that is kind of a
regression with
respect to what the changelog says), I'm closing this vote and will
start a new in a jiff.

Sorry everyone.

--
Sylvain

On Tue, Oct 11, 2011 at 4:53 PM, Brandon Williams <dr...@gmail.com> wrote:
> On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne <sy...@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).
>
> Unfortunately, I think
> https://issues.apache.org/jira/browse/CASSANDRA-3346 is a regression
> that will warrant another re-roll. :(
>
> Third time's the charm?
>
> -Brandon
>

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Brandon Williams <dr...@gmail.com>.
On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne <sy...@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).

Unfortunately, I think
https://issues.apache.org/jira/browse/CASSANDRA-3346 is a regression
that will warrant another re-roll. :(

Third time's the charm?

-Brandon

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Jonathan Ellis <jb...@gmail.com>.
+1

On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne <sy...@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@r1180970
> 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)
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Stephen Connolly <st...@gmail.com>.
+1 (non-binding)

-Stephen

On 10 October 2011 17:24, Sylvain Lebresne <sy...@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@r1180970
> 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)
>

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Gary Dusbabek <gd...@gmail.com>.
+1

On Mon, Oct 10, 2011 at 11:24, Sylvain Lebresne <sy...@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@r1180970
> 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)
>

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Jonathan Ellis <jb...@gmail.com>.
+1

On Tue, Oct 11, 2011 at 8:32 AM, Brandon Williams <dr...@gmail.com> wrote:
> On Tue, Oct 11, 2011 at 8:29 AM, Sylvain Lebresne <sy...@datastax.com> wrote:
>> 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.
>
> +1.  I agree there is absolutely zero chance of this breaking anything.
>
> -Brandon
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Brandon Williams <dr...@gmail.com>.
On Tue, Oct 11, 2011 at 8:29 AM, Sylvain Lebresne <sy...@datastax.com> wrote:
> 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.

+1.  I agree there is absolutely zero chance of this breaking anything.

-Brandon

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Sylvain Lebresne <sy...@datastax.com>.
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 <bb...@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" <sy...@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)
>
>

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Todd Burruss <bb...@expedia.com>.
That was exactly the problem, thx.  (I'm starting a new thread to chat
about it)

On 10/11/11 6:31 AM, "Sylvain Lebresne" <sy...@datastax.com> wrote:

>@Todd You're likely doing something wrong with your ByteBuffers. It's
>*very* easy
>to screw up with those.
>
>--
>Sylvain
>
>On Tue, Oct 11, 2011 at 7:30 AM, Todd Burruss <bb...@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.jav
>>a:
>> 89)
>>        at
>> 
>>org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.jav
>>a:
>> 36)
>>        at
>> 
>>org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnF
>>am
>> ilySerializer.java:143)
>>        at
>> 
>>org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnF
>>am
>> ilySerializer.java:135)
>>        at
>> 
>>org.apache.cassandra.db.ColumnFamilySerializer.deserialize(ColumnFamilySe
>>ri
>> alizer.java:128)
>>        at
>> 
>>org.apache.cassandra.db.RowMutation$RowMutationSerializer.deserialize(Row
>>Mu
>> 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(AbstractCassan
>>dr
>> aDaemon.java:196)
>>        at
>> 
>>org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCas
>>sa
>> 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.jav
>>a:
>> 89)
>>        at
>> 
>>org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.jav
>>a:
>> 36)
>>        at
>> 
>>org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnF
>>am
>> ilySerializer.java:143)
>>        at
>> 
>>org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnF
>>am
>> ilySerializer.java:135)
>>        at
>> 
>>org.apache.cassandra.db.ColumnFamilySerializer.deserialize(ColumnFamilySe
>>ri
>> alizer.java:128)
>>        at
>> 
>>org.apache.cassandra.db.RowMutation$RowMutationSerializer.deserialize(Row
>>Mu
>> 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(AbstractCassan
>>dr
>> aDaemon.java:196)
>>        at
>> 
>>org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCas
>>sa
>> 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" <sy...@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@r118
>>>09
>>>70
>>>Artifacts:
>>>https://repository.apache.org/content/repositories/orgapachecassandra-04
>>>6/
>>>org/apache/cassandra/apache-cassandra/1.0.0/
>>>Staging repository:
>>>https://repository.apache.org/content/repositories/orgapachecassandra-04
>>>6/
>>>
>>>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)
>>
>>


Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Sylvain Lebresne <sy...@datastax.com>.
@Todd You're likely doing something wrong with your ByteBuffers. It's
*very* easy
to screw up with those.

--
Sylvain

On Tue, Oct 11, 2011 at 7:30 AM, Todd Burruss <bb...@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" <sy...@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)
>
>

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

Posted by Todd Burruss <bb...@expedia.com>.
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" <sy...@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)