Re: Diagnosing memory issues

2012-12-11 Thread Mike
Thank you for the response. Since the time of this question, we've identified a number of areas that needed improving and have helped things along quite a bit. To answer your question, we were seeing both ParNew and CMS. There were no errors in the log, and all the nodes have been up. Howe

Re: Diagnosing memory issues

2012-12-04 Thread aaron morton
For background, a discussion on estimating working set http://www.mail-archive.com/user@cassandra.apache.org/msg25762.html . You can also just look at the size of tenured heap after a CMS. Are you seeing lots of ParNew or CMS ? GC activity is a result of configuration *and* workload. Look in y