[
https://issues.apache.org/jira/browse/SOLR-6851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-6851:
---------------------------------
Attachment: SOLR-6851.patch
When I got into dealing with the oom script issue Hossman found, we realized
that the PID handling was sub-optimal and overall needed to vet out issues
related to running Solr as a service using an /etc/init.d/solr script. This
patch has a very simple solution for that.
I'm working on a Taking Solr to Production page for the ref guide to explain
how to structure your environment and how to use the scripts in production.
> oom_solr.sh problems and other issues that make it hard to run Solr as a
> service on *nix
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-6851
> URL: https://issues.apache.org/jira/browse/SOLR-6851
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Timothy Potter
> Fix For: 5.0
>
> Attachments: SOLR-6851.patch
>
>
> noticed 2 problems with the oom_solr.sh script...
> 1) the script is only being run with the port of hte solr instance to
> terminate, so the log messages aren't getting writen to the correct directory
> -- if we change hte script to take a log dir/file as an argument, we can
> ensure the logs are written to the correct place
> 2) on my ubuntu linux machine (where /bin/sh is a symlink to "/bin/dash"),
> the console log is recording a script error when java runs oom_solr.sh...
> {noformat}
> #
> # java.lang.OutOfMemoryError: Java heap space
> # -XX:OnOutOfMemoryError="/home/hossman/lucene/5x_dev/solr/bin/oom_solr.sh
> 8983"
> # Executing /bin/sh -c "/home/hossman/lucene/5x_dev/solr/bin/oom_solr.sh
> 8983"...
> /home/hossman/lucene/5x_dev/solr/bin/oom_solr.sh: 20: [: 14305: unexpected
> operator
> Running OOM killer script for process 14305 for Solr on port 8983
> Killed process 14305
> {noformat}
> steps to reproduce: {{bin/solr -e techproducts -m 10m}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
