you will probably also want to get some better visibility into what is going on with your JVM and GC
easiest way is to enable some GC logging options. the following additional options will give you a good deal of information in gc logs -Xloggc:$JETTY_LOGS/gc.log -verbose:gc -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+PrintTenuringDistribution -XX:+PrintClassHistogram -XX:+PrintHeapAtGC -XX:+PrintGCApplicationConcurrentTime -XX:+PrintGCApplicationStoppedTime -XX:+PrintPromotionFailure -XX:+PrintAdaptiveSizePolicy -XX:+PrintTLAB -XX:PrintFLSStatistics=1 -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=10m you may find you have a particular portion of your heap which is undersized using G1GC with the adaptive sizing is a very handy way to deal with the memory usage in solr which can be somewhat difficult to tune optimally using the traditional static ratios (what works well for data ingestion is probably not optimal for searching) once you have a baseline of logs using your existing JVM sizings and the additional logging options above you might try switching from CMS to G1GC with adaptive sizing, and removing all the static tunings for tenuring and ratios and compare to a very minimal G1GC config -XX:+UseG1GC -XX:+UseAdaptiveSizePolicy -XX:MaxGCPauseMillis=1000 -- configuring the JMX interface is another way to get real time views into what is going on using jconsole or jvisualvm tools ________________________________________ From: Otis Gospodnetic <otis.gospodne...@gmail.com> Sent: Thursday, May 29, 2014 07:20 To: solr-user@lucene.apache.org Subject: Re: Solr High GC issue Hi Bihan, That's a lot of parameters and without trying one can't really give you very specific and good advice. If I had to suggest something quickly I'd say: * go back to the basics - remove most of those params and stick with the basic ones. Look at GC and tune slowly by changing/adding params one at a time. * consider using G1 GC with the most recent Java7. Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Thu, May 29, 2014 at 1:36 AM, bihan.chandu <bihan.cha...@gmail.com>wrote: > Hi All > > I am Currently using solr 3.6.1 and my system handle lot of request .Now we > are facing High GC issue in system. Please find the memory parameters in my > solr system . Can some on help me to identify is there any relationship > between my memory parameters and GC issue. > > MEM_ARGS="-Xms7936M -Xmx7936M -XX:NewSize=512M -XX:MaxNewSize=512M > -Xss1024k > -XX:ParallelGCThreads=8 -XX:+UseConcMarkSweepGC > -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseCMSInitiatingOccupancyOnly > -XX:+CMSParallelRemarkEnabled -XX:+AggressiveOpts > -XX:LargePageSizeInBytes=2m -XX:+UseLargePages -XX:MaxTenuringThreshold=15 > -XX:-UseAdaptiveSizePolicy -XX:PermSize=256M -XX:MaxPermSize=256M > -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:+PrintGCDetails > -XX:+PrintGCTimeStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintGC > -Xloggc:${GCLOG} -XX:-OmitStackTraceInFastThrow -XX:+DisableExplicitGC > -XX:-BindGCTaskThreadsToCPUs -verbose:gc -XX:StackShadowPages=20" > > Thanks > Bihan > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-High-GC-issue-tp4138570.html > Sent from the Solr - User mailing list archive at Nabble.com. >
