When the JVM is out of memory, you get OOM exceptions, one of
the characteristics of the op system.
I'd guess that you're not actually in the same environment on both
machines. The Solr admin page will tell you how much memory Solr
_thinks_ it has allocated to the JVM, it's worth checking just
Hi Shawn,
Thanks for the helpful and thorough response. While I understand all of the
factors that you've outlined for memory requirements (in fact, I'd
previously read your page on Solr performance problems), it is baffling to
me why two identical SolrCloud instances, each sharded across 3 machi
On 1/15/2014 3:10 PM, cwhi wrote:
Thanks for the quick reply. I did notice the exception you pointed out and
had some thoughts about it maybe being the client library I'm using to
connect to Solr (C# SolrNet) disconnecting too early, but that doesn't
explain it eventually running out of memory a
Hi Shawn,
Thanks for the quick reply. I did notice the exception you pointed out and
had some thoughts about it maybe being the client library I'm using to
connect to Solr (C# SolrNet) disconnecting too early, but that doesn't
explain it eventually running out of memory altogether. A large index
On 1/15/2014 2:43 PM, cwhi wrote:
I have a SolrCloud installation with about 2 million documents indexed in it.
It's been buzzing along without issue for the past 8 days, but today started
throwing errors on document adds that eventually resulted in out of memory
exceptions. There is nothing fun
