Ah, now server fails after re-start with NullPointer
on the line in CommitLog.java that has "if (!clHeader_.isDirty(id))"
apparently clHeader_ is null.

        at org.apache.cassandra.db.CommitLog.recover(CommitLog.java:342)
        at org.apache.cassandra.db.RecoveryManager.doRecovery(RecoveryManager.java:58)
        at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:91)
        at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:167)

It throws it as many times as many log segments are in the folder.

On Mon, Sep 28, 2009 at 7:32 PM, Igor Katkov <ikatkov@gmail.com> wrote:
Excellent! Many thanks.

It works, but there is a minor thing:
the very first created commit log segment does not get deleted.
Log if filled with lines like
Not safe to delete commit log d:/cassandra-4/data/commitlog\CommitLog-1254177667321.log; dirty is 1,

On Mon, Sep 28, 2009 at 5:21 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
I have a fix now at
https://issues.apache.org/jira/browse/CASSANDRA-459 -- only applies to
current trunk.  When Jun finishes reviewing I will backport to 0.4.

Sorry for the wait,


On Mon, Sep 28, 2009 at 2:40 PM, Igor Katkov <ikatkov@gmail.com> wrote:
> Does anyone else has the same problem with 0.4?
> As far as I know Digg and Rackspace are biggest adopters of Cassandra. They
> must be running 0.3 then.
> On Sun, Sep 27, 2009 at 12:20 PM, Igor Katkov <ikatkov@gmail.com> wrote:
>> full log is here (new)
>> http://www.katkovonline.com/cassandra-log.zip
>> On Sun, Sep 27, 2009 at 12:18 PM, Igor Katkov <ikatkov@gmail.com> wrote:
>>> There is no log lines with "column family 1"
>>> There are only "column family 0"
>>> On Sun, Sep 27, 2009 at 12:02 PM, Jonathan Ellis <jbellis@gmail.com>
>>> wrote:
>>>> we're looking for "column family 1"