Thanks for the response. Does this cache behavior influence the delay in
catching up with cloud? How can we explain solr cloud replication and
what are the option to monitor and take proactive action (such as
initializing, pausing etc) if needed?
On 8/18/15 5:57 AM, Shawn Heisey wrote:
On 8/17/2015 10:53 PM, Rallavagu wrote:
Also, I have noticed that the memory consumption goes very high. For
instance, each node is configured with 48G memory while java heap is
configured with 12G. The available physical memory is consumed almost
46G and the heap size is well within the limits (at this time it is at
8G). Is there a documentation or to understand this behavior? I suspect
it could be lucene related memory consumption but not sure.
This is completely normal. Your total memory usage could have been
47.9GB instead of 46GB and I would still say the same thing.
Solr cannot consume more than the 12GB heap that you have assigned, plus
a little overhead (probably a few hundred MB) for the JVM itself. The
rest of your memory (assuming Solr is the only significant software
installed on the system) is used by the operating system for caching
contents on your disk. Solr *relies* on this behavior (and the
available RAM it requires) for good performance.
https://en.wikipedia.org/wiki/Page_cache
https://wiki.apache.org/solr/SolrPerformanceProblems
Thanks,
Shawn
