Using cassandra-1.0.6 one node fails to start.
java.lang.OutOfMemoryError: Java heap space
at org.apache.cassandra.utils.obs.OpenBitSet.<init>(OpenBitSet.java:104)
at org.apache.cassandra.utils.obs.OpenBitSet.<init>(OpenBitSet.java:92)
at
org.apache.cassandra.utils.BloomFilterSerializer.deserialize(BloomFilterSerializer.java:55)
at
org.apache.cassandra.io.sstable.SSTableReader.loadBloomFilter(SSTableReader.java:308)
at
org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:168)
at
org.apache.cassandra.io.sstable.SSTableReader$1.run(SSTableReader.java:205)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)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` ? ~mck -- "Don't use Outlook. Outlook is really just a security hole with a small e-mail client attached to it." Brian Trosko | http://github.com/finn-no | http://tech.finn.no |
signature.asc
Description: This is a digitally signed message part
