With Java 1.8, I would use the G1 garbage collector. We’ve been running that combination in prod for three years with no problems.
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 Jan 19, 2020, at 9:25 AM, Rajdeep Sahoo <rajdeepsahoo2...@gmail.com> wrote: > > We are using solr 7.7 . Ram size is 24 gb and allocated space is 12 gb. We > have completed indexing after starting the server suddenly heap space is > getting full. > Added gc params , still not working and jdk version is 1.8 . > Please find the below gc params > -XX:NewRatio=2 > -XX:SurvivorRatio=3 > -XX:TargetSurvivorRatio=90 \ > -XX:MaxTenuringThreshold=8 \ > -XX:+UseConcMarkSweepGC \ > -XX:+CMSScavengeBeforeRemark \ > -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 \ > -XX:PretenureSizeThreshold=512m \ > -XX:CMSFullGCsBeforeCompaction=1 \ > -XX:+UseCMSInitiatingOccupancyOnly \ > -XX:CMSInitiatingOccupancyFraction=70 \ > -XX:CMSMaxAbortablePrecleanTime=6000 \ > -XX:+CMSParallelRemarkEnabled > -XX:+ParallelRefProcEnabled > -XX:+UseLargePages \ > -XX:+AggressiveOpts \
