Hi, We are using solr 4.8.1 and getting OOM Error in one of the test environments. Given below are the details:
1. OS - Linux, 64 bit, 32 GB RAM 2. Solr - 4.8.1, 8 GB allocation as java heap. Installed as service. Thread size (-Xss of 256K, -XX:+UseParallelOldGC). 3. Java - 1.7 update 95, 64-bit It is happening when one of the solr instance is trying to come up. It has around 100GB of data, lying on some network storage like NFS. Now, the interesting part is, eclipse MAT plugin shows that FieldCache has taken more than 3.5GB from 8GB. This environment has setup for stress testing solr, so even when a new solr instance is starting, load is on it. What I suspect here is, two things are happening at same time: a. Solr is starting and indexing data (on network). b. Solr is trying to answer client queries. Now, this might be resulting in scenario where millions of new objects are coming in cache and getting de-referenced. hprof file shows that minor GC is happening every 1 minute. Is this a reasonable scenario? Anyone seen/encountered it? Any pointers are welcomed. Feel free to revert in case you need more information. Regards, Prateek Jain
