Re: 3.11.2 memory leak

s a >>>> patch available since March without getting further attention. >>>> >>>> >>>> >>>> Regards, >>>> >>>> Thomas >>>> >>>> >>>> >>>> *From:* Jeff Jirsa [mailto:jji...@gm

Re: 3.11.2 memory leak

;>> >>> 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

ince 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 l

Re: 3.11.2 memory leak

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

Jeff, 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 From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Dienstag, 05. Juni 2018 00:51 To: cassandra Subject: Re: 3.11.2

Re: 3.11.2 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 at 6:52 AM, Ab

Re: 3.11.2 memory leak

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 gott