The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, Freistädterstraße 313
FWIW, when talking about https://issues.apache.org/
jira/browse/CASSANDRA-13929, there is a patch available since March without getting further attention.
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, Abdul Patel <abd786.ap@xxxxxxxxx> wrote:
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 days i again see 80% + usage and its 16gb and above ..which we never saw before .
Seems like memory leak bug?
Does anyone has any idea ? Our 3.11.2 release rollout has been halted because of this.
If not 3.11.2 whats the next best stable release we have now?