[ 
https://issues.apache.org/jira/browse/SOLR-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090458#comment-16090458
 ] 

Amrit Sarkar commented on SOLR-11084:
-------------------------------------

Neil,

This is undocumented actually, and we should comment on the docs for this to 
get included. Here's what's happening ::

solr.sh (solr script) :: line no:: 1334 (master branch)
{code}
if [[ $SOLR_HOME != /* ]] && [[ -d "$SOLR_SERVER_DIR/$SOLR_HOME" ]]; then
      SOLR_HOME="$SOLR_SERVER_DIR/$SOLR_HOME"
      SOLR_PID_DIR="$SOLR_HOME"
{code}

default value of {{SOLR_SERVER_DIR}} is {SOLR_DIR/server/}}
and when we pass: {{SOLR_HOME}} as {{solr}}; it makes a perfect directory 
{{SOLR_DIR/server/solr}} which is legit and it gets accepted.

> 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
>
> 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]

Reply via email to