There have been a couple of threads lately discussing that some OOMs
are not propagated appropriately and thus don't trigger the OOM killer.
Does anyone think this should be a JIRA?
On Fri, Oct 23, 2015 at 7:17 AM, Raja Pothuganti
wrote:
> Hi,
>
> Some times I see
Yes, let's create a JIRA ... looks like the OOM is getting wrapped
which prevents it from propagating correctly to trigger the oom
script:
org.apache.solr.common.SolrException; null:java.lang.RuntimeException:
java.lang.OutOfMemoryError: Java heap space
On Fri, Oct 23, 2015 at 8:28 AM, Erick
done: https://issues.apache.org/jira/browse/SOLR-8193
On Fri, Oct 23, 2015 at 8:16 AM, Timothy Potter wrote:
> Yes, let's create a JIRA ... looks like the OOM is getting wrapped
> which prevents it from propagating correctly to trigger the oom
> script:
>
>
Hi,
Some times I see OOM happening on replicas,but does not trigger script
oom_solr.sh which was passed in as
-XX:OnOutOfMemoryError=/actualLocation/solr/bin/oom_solr.sh 8091.
These OOM happened while DIH importing data from database. Is this known
issue? is there any quick fix? Sent yesterday