Hi Walter, may I give you the advise to _NOT_ set XX:G1HeapRegionSize. That is computed during JAVA start by the engine according to heap and available memory. A wrong set size can even a huge machine with 31GB heap and 157GB RAM force into OOM. Guess how I figured that out, took me about one week to locate it.
Regards Bernd Am 26.03.2018 um 17:08 schrieb Walter Underwood: > We use the G1 collector in Java 8u131 and it works well. We are running > 6.6.2. Our Solr instances do a LOT of allocation. We have long queries (25 > terms average) and many unique queries. > > SOLR_HEAP=8g > # Use G1 GC -- wunder 2017-01-23 > # Settings from https://wiki.apache.org/solr/ShawnHeisey > GC_TUNE=" \ > -XX:+UseG1GC \ > -XX:+ParallelRefProcEnabled \ > -XX:G1HeapRegionSize=8m \ > -XX:MaxGCPauseMillis=200 \ > -XX:+UseLargePages \ > -XX:+AggressiveOpts \ > " > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > >> On Mar 26, 2018, at 1:22 AM, Derek Poh <d...@globalsources.com> wrote: >> >> Hi >> >> From your experience, would like to know if It is advisable to change the gc >> parameters in solr.in.sh or solrfile? >> It is mentioned in the documentation to edit solr.in.sh but would like >> toknow which file you actually edit. >> >> I am using Solr 6.6.2at the moment. >> >> Regards, >> Derek >> >>
