[
https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615391#comment-17615391
]
Shawn Heisey commented on SOLR-8803:
------------------------------------
{quote}"manageProcess" seems scary,
{quote}
I did the best I could to minimize permissions, but there isn't anything
granular for this. Since Solr will almost never be running with root
privileges, I figure it's pretty safe.
{quote}maybe would be good to check if pid == 0 when doing the warn/info
logging.
{quote}
Good idea. In the newest patch, I have set up different logging if it's not
able to get the PID. I did switch back to logging the full exception in the
event of failure, since I can't predict what the problem will be. I solved the
massive exception I was getting by giving the manageProcess permission, so I
figure if somebody has a problem with that, the whole exception should get
logged.
> 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.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]
