[
https://issues.apache.org/jira/browse/SOLR-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-11084:
--------------------------------
Attachment: SOLR-11084.patch
Does this looks good. I have extended Neil's patch. Added the help text.
{code}
-s <dir> Sets the solr.solr.home system property; Solr will create core
directories under
this directory. This allows you to run multiple Solr
instances on the same host
while reusing the same server directory set using the -d
parameter. If set, the
specified directory should contain a solr.xml file, unless
solr.xml exists in Zookeeper.
This parameter is ignored when running examples (-e), as the
solr.solr.home depends
on which example is run. The default value is server/solr. If
passed relative dir,
validation with current dir will be done, before trying
default server/<dir>
{code}
> Issue with starting script with solr.home (-s) == solr
> ------------------------------------------------------
>
> Key: SOLR-11084
> URL: https://issues.apache.org/jira/browse/SOLR-11084
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.6
> Environment: OS X 10.12
> Reporter: Neil Ireson
> Attachments: SOLR-11084.patch, SOLR-11084.patch
>
>
> I've just hit an issue when starting solr using the script. All works well
> when I use:
> /solr-6.6.0/bin/solr start -p 9090 -m 4g -s data/solr
> However if I cd into the data directory and try:
> /solr-6.6.0/bin/solr start -p 9090 -m 4g -s solr
> Then I get no cores loaded and the "solr.solr.home" shown in the UI as my
> installation solr (i.e. /solr-6.6.0/server/solr)
> I thought that "solr" may be a reserved word so I changed the name of my
> folder to "test-solr" and this worked.
> I'm unsure if this is an undocumented feature (at least I couldn't find any
> reference to it) or a bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
