If you're OOMing on restart you WILL OOM during normal usage given
heavy enough write load. Definitely adjust memtable thresholds down
or, as Dominic suggests, upgrade to 0.8.
On Tue, Jun 21, 2011 at 12:02 PM, Dominic Williams
wrote:
> Hi gabe,
> What you need to do is the following:
> 1. Adjust
Hi gabe,
What you need to do is the following:
1. Adjust cassandra.yaml so when this node is starting up it is not
contacted by other nodes e.g. set thrift to 9061 and storage to 7001
2. Copy your commit logs to tmp sub-folder e.g. commitLog/tmp
3. Copy a small number of commit logs back into m
AFAIK the node will not announce itself in the ring until the log replay is
complete, so it will not get the schema update until after log replay. If
possible i'd avoid making the schema change until you have solved this problem.
My theory on OOM during log replay is that the high speed inserts
Hi,
Cassandra: 7.6-2
I was restarting a node and ran into OOM while replaying the commit log. I
am not able to bring the node up again.
DEBUG 15:11:43,501 forceFlush requested but everything is clean
< For this I don't know what to do.
java.lang.OutOfMemoryError: Java heap space
at
