cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <>
Subject Re: Pushing through major compaction
Date Fri, 30 Mar 2012 23:55:56 GMT
If you are experiencing OOM related to compaction try the following:

* if you have wide rows reduce the in_memory_compaction_limit_in_mb yaml setting. 
* uncomment  concurrent_compactors so that a single compaction run at a time

Hope that helps. 

Aaron Morton
Freelance Developer

On 28/03/2012, at 8:57 AM, Oleg Proudnikov wrote:

> Hello,
> Could you please share you experience on pushing through a major compaction on a CF with
a large number of sstables? I get an OOM even after dropping CFs that I can drop and increasing
JVM heap to the limit. My caches are minimal and memtables are empty. This only happens on
a single node.
> Caused by: java.lang.OutOfMemoryError: Java heap space
>        at<init>(
>        at<init>(
>        at
>        at org.apache.cassandra.db.compaction.CompactionIterator.getCollatingIterator(
>        at org.apache.cassandra.db.compaction.CompactionIterator.<init>(
>        at org.apache.cassandra.db.compaction.CompactionManager.doCompactionWithoutSizeEstimation(
>        at org.apache.cassandra.db.compaction.CompactionManager.doCompaction(
>        at org.apache.cassandra.db.compaction.CompactionManager$
>        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>        at Source
> What other options do I have, e.g. reloading this CF or just the segment from this node?
Ideally I would like to avoid custom export/import scripting. 
> Thank you very much,
> Oleg

View raw message