[
https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-8803:
-------------------------------
Attachment: SOLR-8803-5.patch
Status: Patch Available (was: Patch Available)
New patch. I have now specified the crash file location in the logs directory
instead of the temp dir. This code still gets the PID. What I am hoping is
that the ErrorFile value passed in can be obtained from the JVM so I can remove
the manageProcess permission. I have asked the gc-hotspot-use mailing list at
openjdk.net if that is available.
> OOM killer for Windows
> ----------------------
>
> 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: 9.2
>
> Attachments: SOLR-8803-1.patch, SOLR-8803-2.patch, SOLR-8803-3.patch,
> SOLR-8803-4.patch, SOLR-8803-5.patch, SOLR-8803.patch, oom_win.cmd
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
