You were right. I've attached VisualVM to the process and forced a
System.gc(): used memory went down to near 1.8gb.
So, i don't understand VisualVM dump reports. It said that all those char[]
references have a SolrDispatchFilter instance as CG root.
Another example (1M+ references with the exact
Thanks for the quick answer.
We are experiencing slower indexing speed (x2/x2.5 time consumed) and the
memory consumed during this process oscilates between 10g (max allowed, so
JVM performs full gc's) and 8gb, but never goes under 8gb.
I'll try your suggestions and see how it goes.
Thanks!
El
Hmmm, first time I've seen this, but are you seeing a problem
or is this just a theoretical concern? There are some
references that are held around until GC, these could be
perfectly legitimate, unused but un-collected references.
What I'd try before worrying much:
1> attach jconsole and press the
Hi all, we are facing a high memory usage in our Solr 3.6 master (not in
the slaves) even during "idle" (non indexing) periods.
container: Tomcat 6.0.29
maxthreads: 1.5k (i think this setting is wrong, 300 would be enough)
solr: solr 3.6.0
setup: multitenant environment with 120+ cores and near 5M
