cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Coli <rc...@eventbrite.com>
Subject Re: OOM(Java heap space) on start-up during commit log replaying
Date Tue, 12 Aug 2014 17:31:39 GMT
On Tue, Aug 12, 2014 at 9:34 AM, jivko donev <jivko_d88@yahoo.com> wrote:

> We have a node with commit log director ~4G. During start-up of the node
> on commit log replaying the used heap space is constantly growing ending
> with OOM error.
>
> The heap size and new heap size properties are - 1G and 256M. We are using
> the default settings for commitlog_sync, commitlog_sync_period_in_ms
> and commitlog_segment_size_in_mb.
>

What version of Cassandra?

1G is tiny for cassandra heap. There is a direct relationship between the
data in the commitlog and memtables and in the heap. You almost certainly
need more heap or less commitlog.

=Rob

Mime
View raw message