Shawn, you are right. * OS vendor and version CentosOS 6.5 * Java vendor and version OpenJDK version 1.8.0_20 OpenJDK 64-bit Server VM (build 25.20-b23)
* Servlet container used to start Solr. Catalina(tomcat7) * Total amount of memory in the server. 30 GB * Max heap size for Solr. 8GB(JVM) * An idea of exactly what is running on the server. On our servers runs solr service only and splunk forwarder * Total index size and document count being handled by Solr (add up all indexes). 60GB and 2.6 milion on one shard * A screen shot of a process list sorted by memory usage. <http://lucene.472066.n3.nabble.com/file/n4322362/20170226_102812.jpg> * A screenshot showing total system memory allocations <http://lucene.472066.n3.nabble.com/file/n4322362/20170226_102007.jpg> -- View this message in context: http://lucene.472066.n3.nabble.com/maxwarmingSearchers-and-memory-leak-tp4321937p4322362.html Sent from the Solr - User mailing list archive at Nabble.com.
