Hi, There are a couple of things based on your configuration I can suggest.
-XX:ConcGCThreads=4 - try removing this restriction on the threads. -Xms30g - you should re-consider this param, as 30 GB is huge heap size. Instead, in SolrCloud, try spawning multiple instances if you have system resources. I work on SolrCloud where each server handles 10k read rpm, and found a 12 GB heap to be more than enough. Also, I found 1:2 ratio (NewRatio=2) to be more optimal than 1:3. Thanks, Samuel On Fri, Nov 10, 2017 at 11:52 AM, 胡一博 <huyibo1...@163.com> wrote: > Hello everyone! > > > I run a solr cloud on version 5.5.1. > Sometime ,the ygc time would increase from 0.1s to 10+seconds and keep > 10+seconds for several hours.Even after I trigger a fullgc ,the ygc still > cost 10+seconds. > This happened seldom. > jvm params:(java version "1.7.0_60", Java HotSpot (TM) 64-Bit Server > VM(build 24.60-b09, mixed mode)) > -XX:+CMSParallelRemarkEnabled > -XX:+CMSScavengeBeforeRemark > -XX:+ParallelRefProcEnabled > -XX:+UseCMSInitiatingOccupancyOnly > -XX:+UseConcMarkSweepGC > -XX:+UseParNewGC > -XX:+CMSFullGCsBeforeCompaction=1 > -XX:+CMSInitiatingOccupancyFraction=80 > -XX:ConcGCThreads=4 > -XX:MaxTenuringThreshold=8 > -XX:NewRatio=3 > -XX:ParallelGCThreads=4 > -XX:SurvivorRatio=4 > -XX:TargetSurvivorRatio=90 > -Xms30g > -Xmx30g > -Xss256k
