The Solr logs should have a much more complete stack trace if you can
locate them.
1G of memory is very little for any serious Solr. I'm assuming you
restarted Solr after the
OOM, but Java isn't entirely reliable after an OOM.
FWIW,
Erick
On Mon, Jan 11, 2016 at 6:34 PM, Kelly, Frank wrote:
>
Using Solr 5.3.1 in Solr Cloud mode deployed on AWS (each Solr instance has
-Xmx 1024m and the server has 8GB of RAM)
Am getting a 500 error running a query via the UI
Looking in the logs I just see this with no stack trace
2016-01-12 02:04:22.181 ERROR (qtp59559151-7313) [c:qa_us-east-1_here_a
