Brian:
Many thanks for letting us know what you found. I’ll attach this to SOLR-13003
which is about this exact issue but doesn’t contain this information. This is a
great help.
> On May 2, 2019, at 6:15 AM, Brian Ecker wrote:
>
> Just to update here in order to help others that might run in
Just to update here in order to help others that might run into similar
issues in the future, the problem is resolved. The issue was caused by the
queryResultCache. This was very easy to determine by analyzing a heap dump.
In our setup we had the following config:
In reality this maxRamMB="3072"
On 4/23/2019 11:48 AM, Brian Ecker wrote:
I see. The other files I meant to attach were the GC log (
https://pastebin.com/raw/qeuQwsyd), the heap histogram (
https://pastebin.com/raw/aapKTKTU), and the screenshot from top (
http://oi64.tinypic.com/21r0bk.jpg).
I have no idea what to do with the
Thanks for your response. See below please for detailed responses.
On Tue, Apr 23, 2019 at 6:04 PM Shawn Heisey wrote:
> On 4/23/2019 6:34 AM, Brian Ecker wrote:
> > What I’m trying to determine is (1) How much heap does
> > this setup need before it stabilizes and stops crashing with OOM errors
On 4/23/2019 6:34 AM, Brian Ecker wrote:
What I’m trying to determine is (1) How much heap does
this setup need before it stabilizes and stops crashing with OOM errors,
(2) can this requirement somehow be reduced so that we can use less
memory, and (3) from the heap histogram, what is actually
