[
https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621227#comment-17621227
]
Shawn Heisey commented on SOLR-8803:
------------------------------------
{quote}Or copy Solr to the correct installation location "c:\Program Files"
folder.
{quote}
I have never actually installed Solr on Windows. And in the few places where I
have a Windows install (which are all Windows 10), the username is simple with
no spaces or other special characters.
I tend to put any code in a C:\Users\elyograg\git directory. I can create a
subdirectory there named something like "Solr (test)" and check out the code
there. That should detect most escaping problems.
I did figure out how to get Solr to build on Windows in a standard command
prompt. You just need to install perl. I know that Strawberry Perl works, I
think ActivePerl and most other perl packages for Windows would also work.
> 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: 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: [email protected]
For additional commands, e-mail: [email protected]
