Upgrade from 2.0.3. There are several bugs,
On Wednesday, February 19, 2014, Yogi Nerella wrote:
> You should start your Cassandra daemon with -verbose:gc (please check
syntax) and then run it in foreground, as Cassandra closes the standard out)
> Please see other emails in this forum for getting
You should start your Cassandra daemon with -verbose:gc (please check
syntax) and then run it in foreground, as Cassandra closes the standard out)
Please see other emails in this forum for getting Garbage Collection
Statistics from Cassandra user mail, or look at any Java specific sites.
Ex:
http:
How do I get that statistic?
On Wed, Feb 19, 2014 at 10:34 PM, Yogi Nerella wrote:
> Could be your -Xmn800M is too low, that is why it is trying garbage
> collecting very frequently.
> Do you have any statistics on how much memory it is collecting on every
> cycle?
>
>
>
> On Wed, Feb 19, 2014 a
Could be your -Xmn800M is too low, that is why it is trying garbage
collecting very frequently.
Do you have any statistics on how much memory it is collecting on every
cycle?
On Wed, Feb 19, 2014 at 8:47 AM, Sourabh Agrawal wrote:
> Below is CPU usage from top. I don't see any steal. Idle time
Below is CPU usage from top. I don't see any steal. Idle time is pretty low.
Cpu(s): 83.3%us, 14.5%sy, 0.0%ni, 0.5%id, 0.0%wa, 0.0%hi, 1.7%si,
0.0%st
Any other pointers?
On Wed, Feb 19, 2014 at 8:34 PM, Nate McCall wrote:
> You may be seeing steal from another tenant on the VM. This art
You may be seeing steal from another tenant on the VM. This article has a
good explanation:
http://blog.scoutapp.com/articles/2013/07/25/understanding-cpu-steal-time-when-should-you-be-worried
In short, kill the instance and launch a new one. Depending on your latency
requirements and operational
