Chris,
I've deployed the patch to the cluster for two days. Everything is quite
good since then.
Thank you!
best regards,
韩竹(Zhu Han)
On Sat, Jul 30, 2011 at 3:52 AM, Chris Burroughs
wrote:
> Thanks to everyone who responded (I think I learned a few new tricks
> from seeing what you tried an
Thanks to everyone who responded (I think I learned a few new tricks
from seeing what you tried and how your monitor). I didn't see any
patterns in JVM, OS, cassandra versions etc.
At this time I'm confident in saying CASSANDRA-2868 (and thus really
http://bugs.sun.com/bugdatabase/view_bug.do?bug
I finally upgraded to 0.7.4 -> 0.8.0 (using riptano packages) 2 days ago.
Before, my resident memory (for the java process) would slowly grow without
bound and the OS would kill the process. But, over the last 2 days, I
_think_ it's been stable. I'll let you know in a week :-)
My other stats:
AW
rom: "Sasha Dolgy"
> To: user@cassandra.apache.org
> Sent: Tuesday, July 12, 2011 10:23:02 PM
> Subject: Re: Survey: Cassandra/JVM Resident Set Size increase
>
> I'll post more tomorrow ... However, we set up one node in a single node
> cluster and have left it with no dat
Re: Survey: Cassandra/JVM Resident Set Size increase
I'll post more tomorrow ... However, we set up one node in a single node
cluster and have left it with no datareviewing memory consumption
graphs...it increased daily until it gobbled (highly technical term) all
memory...the system is n
I'll post more tomorrow ... However, we set up one node in a single node
cluster and have left it with no datareviewing memory consumption
graphs...it increased daily until it gobbled (highly technical term) all
memory...the system is now running just below 100% memory usagewhich i
find pec
### Preamble
There have been several reports on the mailing list of the JVM running
Cassandra using "too much" memory. That is, the resident set size is
>>(max java heap size + mmaped segments) and continues to grow until the
process swaps, kernel oom killer comes along, or performance just
degra
