cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <>
Subject Re: exception during startup
Date Tue, 08 Dec 2009 02:34:23 GMT
Patch attached to the jira issue.  Please give it a try if you are
running trunk or the 0.5 beta.  If this is data you care about, you
should make a copy of the commitlog files, just in case. :)

On Mon, Dec 7, 2009 at 8:11 PM, Jonathan Ellis <> wrote:
> on log replay, cassandra cheats and puts all the changes into memory
> before writing to disk, bypassing the normal "is this memtable full
> yet" checks.  this is an optimization but IMO it's misguided because
> it can lead to OOM on replay when you wouldn't OOM for the same set of
> changes during normal operation.
> I've created to
> fix this, but the fix may be a little involved, so if you can
> temporarily give Cassandra more memory to finish the replay, that is
> the easiest workaround and you can set it back the way it was once
> replay completes successfully.
> On Mon, Dec 7, 2009 at 6:59 PM, Brian Burruss <> wrote:
>> wanted to pass this along ... i have 2G RAM allocated to cassandra.  should it need
more?  what are the factors that determine the amount of memory required?
>> thx!
>> 2009-12-07 16:56:30,787 ERROR [main] [] Exception encountered
during startup.
>> java.lang.OutOfMemoryError: Java heap space
>>        at org.apache.cassandra.db.CommitLog.recover(
>>        at org.apache.cassandra.db.RecoveryManager.doRecovery(
>>        at org.apache.cassandra.service.CassandraDaemon.setup(
>>        at org.apache.cassandra.service.CassandraDaemon.main(

View raw message