What's your queries look like? Especially FQs, facets, sort, etc. All of those things require caches of various sorts.
Regards, Alex. Personal: http://www.outerthoughts.com/ and @arafalov Solr resources and newsletter: http://www.solr-start.com/ and @solrstart Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 On 16 December 2014 at 11:55, Trilok Prithvi <trilok.prit...@gmail.com> wrote: > We are getting OOME pretty often (every hour or so). We are restarting > nodes to keep up with it. > > Here is our setup: > SolrCloud 4.10.2 (2 shards, 2 replicas) with 3 zookeepers. > > Each node has: > 16GB RAM > 2GB JVM (Xmx 2048, Xms 1024) > ~100 Million documents (split among 2 shards - ~50M on each shard) > Solr Core is about ~16GB of data on each node. > > *Physical Memory is almost always 99% full.* > > > The commit setup is as follows: > > <updateHandler class="solr.DirectUpdateHandler2"> <updateLog> <str name= > "dir">${solr.ulog.dir:}</str> </updateLog> <autoCommit> <maxTime>300000</ > maxTime> <maxDocs>100000</maxDocs> <openSearcher>false</openSearcher> </ > autoCommit> <autoSoftCommit> <maxTime>5000</maxTime> </autoSoftCommit> </ > updateHandler> > Rest of the solrconfig.xml setup is all default. > > Some of the errors that we see on Solr ADMIN Logging is as follows: > > java.lang.OutOfMemoryError: Java heap space > > org.apache.solr.common.SolrException: no servers hosting shard: > > org.apache.http.TruncatedChunkException: Truncated chunk ( expected > size: 8192; actual size: 7222) > > > Please let me know if you need anymore information. > > > Thanks!
