[
https://issues.apache.org/jira/browse/SOLR-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170368#comment-14170368
]
Shawn Heisey commented on SOLR-6549:
------------------------------------
Paraphrasing some thoughts that I expressed on IRC:
{quote}
If the -s option is used, the argument could be tested. If it's not a
directory, a startup warning can be logged, or the script could even abort. If
solr.xml does not exist in the directory indicated, a warning could be printed.
A lack of solr.xml should abort, because the user might have solr.xml in
zookeeper, or they might be intentionally trying to start in single-core mode.
(Related: single-core mode probably should be nuked from 5.0, if it's not
already)
Perhaps a -q option could be implemented to suppress startup warnings. If the
script sources /etc/default/solr (or some other filename), options could be
picked up from that file.
{quote}
I see that after I said these things and started transferring my thoughts here,
[~thelabdude] replied on IRC, saying that the script already does check for the
existence of both the solr home and solr.xml, then disappeared. I admit that I
did not look at the script before speaking. Have to stop doing that! I think
the existing checks can be improved, will think about it.
> bin/solr script should support a -s option to set the -Dsolr.solr.home
> property
> -------------------------------------------------------------------------------
>
> Key: SOLR-6549
> URL: https://issues.apache.org/jira/browse/SOLR-6549
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Reporter: Timothy Potter
> Assignee: Timothy Potter
> Fix For: 4.10.2, 5.0
>
>
> The bin/solr script supports a -d parameter for specifying the directory
> containing the webapp, resources, etc, lib ... In most cases, these binaries
> are reusable (and will eventually be in a server directory SOLR-3619) even if
> you want to have multiple solr.solr.home directories on the same server. In
> other words, it is more common/better to do:
> {code}
> bin/solr start -d server -s home1
> bin/solr start -d server -s home2
> {code}
> than to do:
> {code}
> bin/solr start -d server1
> bin/solr start -d server2
> {code}
> Basically, the start script needs to support a -s option that allows you to
> share binaries but have different Solr home directories for running multiple
> Solr instances on the same host.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
