[
https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701466#comment-17701466
]
Shawn Heisey commented on SOLR-8803:
------------------------------------
I looked into the docker build tree and could find no evidence that it actually
listens to the OOM variable mentioned in the reference guide. Setting OOM to
exit, crash, or script produced no difference in the commandline used to run
solr inside the container.
> 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
