lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-12777) Add bin/solr args for specifying PID and LOGS dirs
Date Tue, 18 Sep 2018 12:28:00 GMT


Jan Høydahl commented on SOLR-12777:

Thanks for the feedback. I changed the issue to "Improvement" and the title to your primary
suggestion "Add bin/solr args for specifying PID and LOGS dirs".

I agree that it would be great to have deb and rpm packages but until now the project has
delegated that to be produced downstream by the wider ecosystem. You could always suggest
that the project should own the release process of such packages too (as we do with zip, tgz,
maven) but for that to work there will have to be committers available with both knowledge
and interest of doing that work. There are already volunteers maintaining "brew" packages
for macOS and "chocolatey" packages for Windows.

> Add bin/solr args for specifying PID and LOGS dirs
> --------------------------------------------------
>                 Key: SOLR-12777
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>    Affects Versions: 7.3.1
>            Reporter: Pete Ryland
>            Priority: Major
> When starting solr, an optional {{-d}} parameter can be provided.  This specifies the
"Solr server directory" which needs to be the {{server}} directory from the raw distribution. 
This clearly contains the program files, so as per common practice should not be writable
by the user running the program.  However, when specified, an error results because it tries
to create a log directory within the program directory!  This is really really bad practice.
 One should be able to specify a directory for the runtime files and log files on the command
line.  It would be even better if the defaults conformed to the filesystem hierarchy standard
when run on a Linux system.  I understand that you want to make it easy for developers to
use your software, but when deploying on actual production systems, these things are really
important.  It's also important to understand that the people deploying your software to production
are different to the ones who develop with your software, and a deep understanding of your
software shouldn't be necessary for the former to be able to deploy it.
> A wholly-unsatisfactory workaround is to set the pid and log directories by environment
variable before starting the server:
> {{$ export SOLR_PID_DIR=/var/lib/celum-search}}
> {{$ export SOLR_LOGS_DIR=/var/log/celum-search}}
> This can also be done in {{/etc/default/}}.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message