Then you'll want to use MAT to analyze the dump the JVM gave you of
the heap at OOM time. (http://www.eclipse.org/mat/)
On Tue, Jul 12, 2011 at 3:22 PM, Anurag Gujral wrote:
> Hi Jonathan,
> Thanks for your mail. But no-one of the things
> mentioned in the link pertains to O
Hi Jonathan,
Thanks for your mail. But no-one of the things
mentioned in the link pertains to OOM error I we are seeing.
thanks
Anurag
On Tue, Jul 12, 2011 at 10:42 AM, Jonathan Ellis wrote:
> Have you seen
> http://www.datastax.com/docs/0.8/troubleshooting/index#nodes-are-d
Have you seen
http://www.datastax.com/docs/0.8/troubleshooting/index#nodes-are-dying-with-oom-errors
?
On Mon, Jul 11, 2011 at 1:55 PM, Anurag Gujral wrote:
> Hi All,
> I am getting following error from cassandra:
> ERROR [ReadStage:23] 2011-07-10 17:19:18,300
> DebuggableThreadPoolEx
Are you on a 64 bit VM? A 32 bit vm will basically ignore any setting over
2GB
On Mon, Jul 11, 2011 at 4:55 PM, Anurag Gujral wrote:
> Hi All,
>I am getting following error from cassandra:
> ERROR [ReadStage:23] 2011-07-10 17:19:18,300
> DebuggableThreadPoolExecutor.java (line 103) E
Hi All,
I am getting following error from cassandra:
ERROR [ReadStage:23] 2011-07-10 17:19:18,300
DebuggableThreadPoolExecutor.java (line 103) Error in ThreadPoolExecutor
java.lang.OutOfMemoryError: Java heap space
at
org.apache.cassandra.utils.BloomFilterSerializer.deserialize(B
