On 2/9/24 06:58, Ishan Chattopadhyaya wrote:
Solr reports a memory usage of nearly 100%. This, I believe, is good as
that indicates full memory utilization by MMapDirectory.

In case Solr is saying that 100% of the 2GB heap memory is used, it is not
a good thing.

It can be very normal for the JVM memory to show 100% used. If it STAYS at 100% when refreshing the page often over the course of several minutes during heavy usage, that probably indicates the heap should be increased.

You should set Xms and Xmx to the same value. Using 'SOLR_HEAP=NNN' instead of SOLR_JAVA_MEM will accomplish this. Something like SOLR_HEAP=2g for the value you are going for.

If the Physical Memory is at 100%, there's not enough info in the Solr dashboard to indicate WHAT is using the memory. If Solr is the only thing running in the container, then most of the memory is probably consumed by the OS disk cache, which backs files opened with mmap.

What are the details about the indexes served by that Solr instance? Looking for total document count and total index size.

It might make no difference in the advice given, but the Solr version is not given. The mailing list ate your attachments, so we can't see those.

Thanks,
Shawn

Reply via email to