Re: 3.11.2 memory leak

2018-07-22 Thread kurt greaves
t;>> patch available since March without getting further attention. >>>> >>>> >>>> >>>> Regards, >>>> >>>> Thomas >>>> >>>> >>>> >>>> *From:* Jeff Jirsa [mailto:jji...@gmail.com] &

Re: 3.11.2 memory leak

2018-07-22 Thread Abdul Patel
gt;>> >>> FWIW, when talking about https://issues.apache.org/ >>> jira/browse/CASSANDRA-13929, there is a patch available since March >>> without getting further attention. >>> >>> >>> >>> Regards, >>> >>> Thomas >>>

Re: 3.11.2 memory leak

2018-06-19 Thread kurt greaves
without getting further attention. >> >> >> >> Regards, >> >> Thomas >> >> >> >> *From:* Jeff Jirsa [mailto:jji...@gmail.com] >> *Sent:* Dienstag, 05. Juni 2018 00:51 >> *To:* cassandra >> *Subject:* Re: 3.11.2 memory leak >&g

Re: 3.11.2 memory leak

2018-06-19 Thread Abdul Patel
a patch available since March > without getting further attention. > > > > Regards, > > Thomas > > > > *From:* Jeff Jirsa [mailto:jji...@gmail.com] > *Sent:* Dienstag, 05. Juni 2018 00:51 > *To:* cassandra > *Subject:* Re: 3.11.2 memory leak > > >

RE: 3.11.2 memory leak

2018-06-04 Thread Steinmaurer, Thomas
memory leak There have been a few people who have reported it, but nobody (yet) has offered a patch to fix it. It would be good to have a reliable way to repro, and/or an analysis of a heap dump demonstrating the problem (what's actually retained at the time you're OOM'ing). On Mon, Jun 4, 2018

Re: 3.11.2 memory leak

2018-06-04 Thread Jeff Jirsa
There have been a few people who have reported it, but nobody (yet) has offered a patch to fix it. It would be good to have a reliable way to repro, and/or an analysis of a heap dump demonstrating the problem (what's actually retained at the time you're OOM'ing). On Mon, Jun 4, 2018 at 6:52 AM,

Re: 3.11.2 memory leak

2018-06-04 Thread Elliott Sims
Are you seeing significant issues in terms of performance? Increased garbage collection, long pauses, or even OutOfMemory? Which garbage collector are you using and with what settings/thresholds? Since the JVM's garbage-collected, a bigger heap can mean a problem or it can just mean "hasn't

3.11.2 memory leak

2018-06-04 Thread Abdul Patel
Hi All, I recently upgraded my non prod cluster from 3.10 to 3.11.2. It was working fine for a 1.5 weeks then suddenly nodetool info startee reporting 80% and more memory consumption. Intially it was 16gb configured, then i bumped to 20gb and rebooted all 4 nodes of cluster-single DC. Now after 8