[
https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618082#comment-17618082
]
Shawn Heisey commented on SOLR-8803:
------------------------------------
One thing that is different now: I had been doing most of this on branch_9x,
so I could quickly build a 9.2.0-SNAPSHOT tgz and deploy it on my mail server.
I switched to the main branch when I saw that there were merge conflicts with
trying to do "git pull" to keep my repo up to date, because commits for a
change should happen to main first.
The build runs a lot more slowly with only 5 threads/processes. And if I am
interpreting those "Expiring" messages right, it looks like it is restarting
the gradle daemon quite frequently, which probably also makes things run slower.
> 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-6.patch, SOLR-8803-7.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]
