Dne 25.7.2013 20:03, Andrew Cobley napsal(a):
Any idea on how I can go about pinpointing the problem to raise a JIRA issue ?
http://www.ehow.com/how_8705297_create-java-heap-dump.html
So is that in Cassandra somewhere ? Any idea on how I can go about pinpointing
the problem to raise a JIRA issue ?
Andy
On 25 Jul 2013, at 17:50, Radim Kolar wrote:
>
>> I'm wondering if it's a GC issue ?
> yes it is:
>
> 1039280992 used; max is 1052770304
>
> most likely memory leak.
>
>
I'm wondering if it's a GC issue ?
yes it is:
1039280992 used; max is 1052770304
most likely memory leak.
I'm getting something similar for beta 2, you can see here it's dropping from
12000 to 400 quite quickly. The output from cassandra is available n dropbox
here:
https://dl.dropboxusercontent.com/u/1638201/output.txt (184kBytes)
I'm wondering if it's a GC issue ?
./cassandra-stress -d 134.36
Some bug was fixed in 2.0.0-beta2 by C* developers. Try it!
2013/7/22 Andrew Cobley
> I've been noticing some strange casandra-stress results with 2.0.0 beta
> 1. I've set up a single node on a Mac (4 gig ram, 2.8Ghz core 2 duo) and
> installed 2.0.0 beta1.
>
> When I run ./cassandra-stress
I've been noticing some strange casandra-stress results with 2.0.0 beta 1.
I've set up a single node on a Mac (4 gig ram, 2.8Ghz core 2 duo) and installed
2.0.0 beta1.
When I run ./cassandra-stress -d 134.36.36.218 I'm seeing the interval-op-rate
drop from a peek of 11562 at the start to 0 -2
