On 5/10/2016 7:46 PM, lltvw wrote: > the args used to start solr are as following, and upload my screen shot to > http://www.yupoo.com/photos/qzone3927066199/96064170/, please help to take a > look, thanks. > > -DSTOP.PORT=7989 > -DSTOP.KEY= > -DzkHost=node1:2181,node2:2181,node3:2181/solr > -Dsolr.solr.home=solr > -Dbootstrap_conf=true > -Xmx10240M > -Xms4196M > -XX:MaxPermSize=512M > -XX:PermSize=256M > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dcom.sun.management.jmxremote.port=3000 > -Dcom.sun.management.jmxremote
You still didn't say how you're starting Solr. I don't see anything in the arguments that I would expect to see if running in tomcat or another third-party container. You have a stop port and a stop key, which suggest that you might be running with the start.jar for the jetty included with Solr. The "bootstrap_conf" system property is not something you should set every time you start SolrCloud. It is designed to be used once, to convert a non-cloud install to a cloud install. In my opinion, it shouldn't even be used once. I don't have any way to confirm this with the information you've sent so far, but one problem you *might* be having is garbage collection pauses. GC tuning is extremely important for Solr. Here's some information I have written on the topic: https://wiki.apache.org/solr/ShawnHeisey#GC_Tuning_for_Solr Thanks, Shawn
