Re: maxwarmingSearchers and memory leak

2017-03-05 Thread SOLR4189
1) We've actually got 60 to 80 GB of index on the machine (in the image below you can see that size of index on the machine 82GB, because all index is in path /opt/solr): 2) Our commits runs: autoSoftCommit - each 15 minutes and autoHard

Re: maxwarmingSearchers and memory leak

2017-03-01 Thread Shawn Heisey
On 2/26/2017 6:40 AM, SOLR4189 wrote: > 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

Re: maxwarmingSearchers and memory leak

2017-02-26 Thread SOLR4189
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)

Re: maxwarmingSearchers and memory leak

2017-02-24 Thread Shawn Heisey
On 2/23/2017 1:51 AM, SOLR4189 wrote: > We have maxwarmingSearchers set to 2 and field value cache set to > initial size of 64. We saw that by taking a heap dump that our caches > consume 70% of the heap size, by looking into the dump we saw that > fieldValueCache has 6 occurences of > org.apache.s