You may want to try upgrading to 3.11.3 instead which has some memory leaks fixes.
On Tue, Aug 28, 2018 at 9:59 AM, Mun Dega <mundeg...@gmail.com> wrote: > I am surprised that no one else ran into any issues with this version. GC > can't catch up fast enough and there is constant Full GC taking place. > > The result? unresponsive nodes makeing entire cluster unusable. > > Any insight on this issue from anyone that is using this version would be > appreciated. > > Ma > > On Fri, Aug 24, 2018, 04:30 Mohamadreza Rostami < > mohamadrezarosta...@gmail.com> wrote: > >> You have very large heap,it’s take most of cpu time in GC stage.you >> should in maximum set heap on 12GB and enable row cache to your cluster >> become faster. >> >> On Friday, 24 August 2018, Mun Dega <mundeg...@gmail.com> wrote: >> >>> 120G data >>> 28G heap out of 48 on system >>> 9 node cluster, RF3 >>> >>> >>> On Thu, Aug 23, 2018, 17:19 Mohamadreza Rostami < >>> mohamadrezarosta...@gmail.com> wrote: >>> >>>> Hi, >>>> How much data do you have? How much RAM do your servers have? How much >>>> do you have a heep? >>>> On Thu, Aug 23, 2018 at 10:14 PM Mun Dega <mundeg...@gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> We recently upgraded from Cassandra 2.1 to 3.11.2 on one cluster. The >>>>> process went OK including upgradesstable but we started to experience high >>>>> latency for r/w, occasional OOM and long GC pause after. >>>>> >>>>> For the same cluster with 2.1, we didn't have any issues like this. We >>>>> also kept server specs, heap, all the same in post upgrade >>>>> >>>>> Has anyone else had similar issues going to 3.11 and what are the >>>>> major changes that could have such a major setback in the new version? >>>>> >>>>> Ma Dega >>>>> >>>>
