cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mick Semb Wever <>
Subject OOM opening bloom filter
Date Sun, 11 Mar 2012 19:47:56 GMT
Using cassandra-1.0.6 one node fails to start.

java.lang.OutOfMemoryError: Java heap space
	at org.apache.cassandra.utils.obs.OpenBitSet.<init>(
	at org.apache.cassandra.utils.obs.OpenBitSet.<init>(
	at org.apache.cassandra.utils.BloomFilterSerializer.deserialize(
	at java.util.concurrent.Executors$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

This happens with (our normal) -Xmx12g setting.

How did this this bloom filter get too big?
Is the best option to keep trying with larger Xmx settings until i can
startup the node and then to do a `nodetool scrub` ?


"Don't use Outlook. Outlook is really just a security hole with a small
e-mail client attached to it." Brian Trosko 

| | |

View raw message