On Wed, Aug 19, 2009 at 9:46 PM, Jonathan Ellisjbel...@gmail.com wrote:
The OOM puzzles me a little; I'm not sure how it could be unable to
replay a mutation that it was able to write to the commitlog in the
first place.
Ah, I think I know: if a compaction starts during recovery, that could
On Wed, Aug 26, 2009 at 12:26 PM, Brian Frank
Coopercoop...@yahoo-inc.com wrote:
Is the commitlog small enough that you can gzip it and attach to JIRA
(10 MB limit)?
/var/cassandra/commitlog has 215 files totaling about 28 GB. Most are 134 MB,
the last one is 6MB. Which one would be useful
: Jonathan Ellis [jbel...@gmail.com]
Sent: Wednesday, August 19, 2009 7:46 PM
To: cassandra-user@incubator.apache.org
Subject: Re: Server cannot startup after shutdown
The malformed input bug was fixed after beta1 and should be in a
nightly build by now. (I introduced a regression where it couldn't
[mailto:jbel...@gmail.com]
Sent: Thursday, August 20, 2009 10:50 AM
To: cassandra-user@incubator.apache.org
Subject: Re: Server cannot startup after shutdown
I saw that you're testing with different tokens now -- how did the
replay OOM work out?
On Wed, Aug 19, 2009 at 10:54 PM, Brian Frank
Coopercoop
The malformed input bug was fixed after beta1 and should be in a
nightly build by now. (I introduced a regression where it couldn't
handle the last entry in the commitlog being incomplete. So upgrading
should be able to restart on the existing commitlogs.)
The OOM puzzles me a little; I'm not
Thanks for the reply. I'll try playing with the memory settings.
brian
From: Jonathan Ellis [jbel...@gmail.com]
Sent: Wednesday, August 19, 2009 7:46 PM
To: cassandra-user@incubator.apache.org
Subject: Re: Server cannot startup after shutdown
