You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Binoy Dalal (JIRA)" <ji...@apache.org> on 2016/03/09 17:15:41 UTC
[jira] [Issue Comment Deleted] (SOLR-8803) OOM killer for Windows
[ https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binoy Dalal updated SOLR-8803:
------------------------------
Comment: was deleted
(was: The only difference between *.bat and *.cmd files I could find is the way in which the scripts return.
For cmd files, certain commands like `set` set the return code while for bat files, the return code is only set on errors.
So I do not think that changing the file extension will make any difference.
I'll do that and run a small test to see if everything works fine and upload the updated files.
Source for the difference info.: http://stackoverflow.com/questions/148968/windows-batch-files-bat-vs-cmd)
> OOM killer for Windows
> ----------------------
>
> Key: SOLR-8803
> URL: https://issues.apache.org/jira/browse/SOLR-8803
> Project: Solr
> Issue Type: Improvement
> Reporter: Binoy Dalal
> Priority: Minor
> Attachments: SOLR-8803.patch, oom_win.bat
>
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org