Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

ive stalls happening on either reading > from disk or flushing dirty pages to disk. > > > > > > *From: *Ben Mills > *Reply-To: *"user@cassandra.apache.org" > *Date: *Monday, November 4, 2019 at 12:14 PM > *To: *"user@cassandra.apache.org" > *Subject: *Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC > > > > CGroup >

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

To: "user@cassandra.apache.org" Subject: Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC CGroup

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

t; > > > *From: *Ben Mills > *Reply-To: *"user@cassandra.apache.org" > *Date: *Monday, November 4, 2019 at 8:51 AM > *To: *"user@cassandra.apache.org" > *Subject: *Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC > > > > *Message from External Se

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

: "user@cassandra.apache.org" Date: Monday, November 4, 2019 at 8:51 AM To: "user@cassandra.apache.org" Subject: Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC Message from External Sender Hi (yet again) Sergio, Finally, note that we use this sidecar<https://urldefens

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi (yet again) Sergio, Finally, note that we use this sidecar for shipping metrics to Stackdriver. It runs as a second container within our Prometheus stateful set. On Mon, Nov 4, 2019 at 8:46 AM Ben Mills wrote: > Hi (again) Serg

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi (again) Sergio, I forgot to note that along with Prometheus, we use Grafana (with Prometheus as its data source) as well as Stackdriver for monitoring. As Stackdriver is still developing (i.e. does not have all the features we need), we tend to use it for the basics (i.e. monitoring and alerti

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi Sergio, Thanks for this and sorry for the slow reply. We are indeed still running Java 8 and so it's very helpful. This Cassandra cluster has been running reliably in Kubernetes for several years, and while we've had some repair-related issues, they are not related to container orchestration

***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi Ben, Well, I had a similar question and Jon Haddad was preferring ParNew + CMS over G1GC for java 8. https://lists.apache.org/thread.html/283547619b1dcdcddb80947a45e2178158394e317f3092b8959ba879@%3Cuser.cassandra.apache.org%3E It depends on your JVM and in any case, I would test it based on you

Re: Memory Recommendations for G1GC

Thanks Sergio - that's good advice and we have this built into the plan. Have you heard a solid/consistent recommendation/requirement as to the amount of memory heap requires for G1GC? On Fri, Nov 1, 2019 at 5:11 PM Sergio wrote: > In any case I would test with tlp-stress or Cassandra stress too

Re: Memory Recommendations for G1GC

ke you’ll end up with your entire database in memory. > > > > *From: *Ben Mills > *Reply-To: *"user@cassandra.apache.org" > *Date: *Friday, November 1, 2019 at 3:31 PM > *To: *"user@cassandra.apache.org" > *Subject: *Memory Recommendations for G1GC

Re: Memory Recommendations for G1GC

In any case I would test with tlp-stress or Cassandra stress tool any configuration Sergio On Fri, Nov 1, 2019, 12:31 PM Ben Mills wrote: > Greetings, > > We are planning a Cassandra upgrade from 3.7 to 3.11.5 and considering a > change to the GC config. > > What is the minimum amount of memory

Re: Memory Recommendations for G1GC

November 1, 2019 at 3:31 PM To: "user@cassandra.apache.org" Subject: Memory Recommendations for G1GC Message from External Sender Greetings, We are planning a Cassandra upgrade from 3.7 to 3.11.5 and considering a change to the GC config. What is the minimum amount of memory that need

Memory Recommendations for G1GC

Greetings, We are planning a Cassandra upgrade from 3.7 to 3.11.5 and considering a change to the GC config. What is the minimum amount of memory that needs to be allocated to heap space when using G1GC? For GC, we currently use CMS. Along with the version upgrade, we'll be running the stateful