[
https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742086#comment-17742086
]
Ovidiu Mihalcea commented on SOLR-8803:
---------------------------------------
??Just to make sure I understand, the {{-XX:+CrashOnOutOfMemoryError}} option
is not stopping the container from restarting, it is just delaying it because
it has to store the crash state??
So from my tests only, because I couldn't find some definitive documentation
for this in Docker context (or what does "the JVM crashes" actually translates
to in actual signals/facts):
+ExitOnOutOfMemoryError gives me the following message: Docker container exited
with non-zero exit code: 3 (SIGKILL probably)
+CrashOnOutOfMemoryError gives: Docker container exited with non-zero exit
code: 143 (SIGTERM)
So from what I can tell CrashOnOutOfMemoryError aims for a more graceful
shutdown.
However, I don't think that is the preferred scenario in a cluster with a high
replica redundancy count.
[~houston] I've found these commits:
[SOLR-8803: Remove docker OOM docs · apache/solr@db853c8
(github.com)|https://github.com/apache/solr/commit/db853c8ae355789d2f4d109271c82d15f19e4f51]
[SOLR-14978 OOM Killer in Foreground (#2055) · apache/solr@7c1ff28
(github.com)|https://github.com/apache/solr/commit/7c1ff288b73b053cc9d17c6d4db4b35ed6c5559a]
Maybe you can remember the reasoning for them? It would really help going
forward with this.
> Generalize OOME handling to work for any OS
> -------------------------------------------
>
> Key: SOLR-8803
> URL: https://issues.apache.org/jira/browse/SOLR-8803
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 9.0
> Reporter: Binoy Dalal
> Assignee: Shawn Heisey
> Priority: Minor
> Labels: OOM, oom
> Fix For: main (10.0), 9.2
>
> Attachments: SOLR-8803-1.patch, SOLR-8803-10.patch,
> SOLR-8803-2.patch, SOLR-8803-3.patch, SOLR-8803-4.patch, SOLR-8803-5.patch,
> SOLR-8803-6.patch, SOLR-8803-7.patch, SOLR-8803-8.patch, SOLR-8803-9.patch,
> SOLR-8803.patch, oom_win.cmd, solr-8803-build-transcript.txt
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Solr on windows does not currently have a script to kill the process on OOM
> errors.
> The idea is to write a batch script that works like the OOM kill script for
> Linux and kills the solr process on OOM errors while creating an OOM log file
> like the one on Linux systems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
