Re: Heap is not released and streaming hangs at 0%

2013-06-27 Thread aaron morton
r 24+ hours of idle time, the JVM needs to >> be restarted to reclaim the heap. >> >> Cheers >> >> - >> Aaron Morton >> Freelance Cassandra Consultant >> New Zealand >> >> @aaronmorton >> http://www.thelastpi

Re: Heap is not released and streaming hangs at 0%

2013-06-26 Thread srmore
>> >>>>- >>>> Aaron Morton >>>> Freelance Cassandra Consultant >>>> New Zealand >>>> >>>> @aaronmorton >>>> http://www.thelastpickle.com >>>> >>>> On 20/06/2013,

Re: Heap is not released and streaming hangs at 0%

2013-06-25 Thread sulong
heap is never released, even after 24+ hours of idle time, the JVM >>> needs to be restarted to reclaim the heap. >>> >>> Cheers >>>> >>>>----- >>>> Aaron Morton >>>> Freelance Cassandra Consultant >>>

Re: Heap is not released and streaming hangs at 0%

2013-06-25 Thread aaron morton
@aaronmorton > http://www.thelastpickle.com > > On 20/06/2013, at 6:36 AM, Wei Zhu wrote: > >> If you want, you can try to force the GC through Jconsole. Memory->Perform >> GC. >> >> It theoretically triggers a full GC and when it will happen depends on the &g

Re: Heap is not released and streaming hangs at 0%

2013-06-21 Thread sankalp kohli
om >>> >>> On 20/06/2013, at 6:36 AM, Wei Zhu wrote: >>> >>> If you want, you can try to force the GC through Jconsole. >>> Memory->Perform GC. >>> >>> It theoretically triggers a full GC and when it will happen depends on >>>

Re: Heap is not released and streaming hangs at 0%

2013-06-21 Thread Bryan Talbot
t;> On 20/06/2013, at 6:36 AM, Wei Zhu wrote: >> >> If you want, you can try to force the GC through Jconsole. >> Memory->Perform GC. >> >> It theoretically triggers a full GC and when it will happen depends on >> the JVM >> >> -Wei >> >&g

Re: Heap is not released and streaming hangs at 0%

2013-06-21 Thread srmore
> > It theoretically triggers a full GC and when it will happen depends on the > JVM > > -Wei > > -- > *From: *"Robert Coli" > *To: *user@cassandra.apache.org > *Sent: *Tuesday, June 18, 2013 10:43:13 AM > *Subject: *Re: Heap is not released and s

Re: Heap is not released and streaming hangs at 0%

2013-06-21 Thread aaron morton
retically triggers a full GC and when it will happen depends on the JVM > > -Wei > > From: "Robert Coli" > To: user@cassandra.apache.org > Sent: Tuesday, June 18, 2013 10:43:13 AM > Subject: Re: Heap is not released and streaming hangs at 0% > > On Tue, Jun 18

Re: Heap is not released and streaming hangs at 0%

2013-06-19 Thread Wei Zhu
3 10:43:13 AM Subject: Re: Heap is not released and streaming hangs at 0% On Tue, Jun 18, 2013 at 10:33 AM, srmore wrote: > But then shouldn't JVM C G it eventually ? I can still see Cassandra alive > and kicking but looks like the heap is locked up even after the traffic is > long st

Re: Heap is not released and streaming hangs at 0%

2013-06-18 Thread Robert Coli
On Tue, Jun 18, 2013 at 10:33 AM, srmore wrote: > But then shouldn't JVM C G it eventually ? I can still see Cassandra alive > and kicking but looks like the heap is locked up even after the traffic is > long stopped. No, when GC system fails this hard it is often a permanent failure which requir

Re: Heap is not released and streaming hangs at 0%

2013-06-18 Thread srmore
Thanks Rob, But then shouldn't JVM C G it eventually ? I can still see Cassandra alive and kicking but looks like the heap is locked up even after the traffic is long stopped. nodetool -h localhost flush didn't do much good. the version I am running is 1.0.12 (I know its due for a upgrade but gott

Re: Heap is not released and streaming hangs at 0%

2013-06-18 Thread Robert Coli
On Tue, Jun 18, 2013 at 8:25 AM, srmore wrote: > I see an issues when I run high traffic to the Cassandra nodes, the heap > gets full to about 94% (which is expected) Which is expected to cause GC failure? ;) But seriously, the reason your node is unable to GC is that you have filled your heap t

Heap is not released and streaming hangs at 0%

2013-06-18 Thread srmore
I see an issues when I run high traffic to the Cassandra nodes, the heap gets full to about 94% (which is expected) but the thing that confuses me is that the heap usage never goes down after the traffic is stopped (at-least, it appears to be so) . I kept the nodes up for a day after stopping the t