[
https://issues.apache.org/jira/browse/SOLR-13618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883427#comment-16883427
]
Erick Erickson commented on SOLR-13618:
---------------------------------------
The original e-mail thread got lost in the translation. This is more about the
fact that the core admin API lets you specify an instanceDir that's outside
SOLR_HOME and puts core.properties there. Then the core isn't found on startup.
We should fail with an informative error. I'll change the title to reflect
that. I agree that letting cores appear anywhere is a bad idea.
I think this has its origin in the old days where every core was specified
explicitly. When we went to core discovery, this slipped through the cracks.
Also, since the core discovery process stops descending the tree when it hits
the first "core,properties", we should probably also fail if there's a
core.properties file either above or below instanceDir under SOLR_HOME..
> Solr start-up fails to discover cores outside SOLR_HOME
> --------------------------------------------------------
>
> Key: SOLR-13618
> URL: https://issues.apache.org/jira/browse/SOLR-13618
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Talvinder Matharu
> Priority: Major
>
> When new 'instanceDir' is set outside the SOLR_HOME directory then core will
> fail to reload after restart as the server only discovers cores within
> SOLR_HOME, looking for a 'core.properties'.
> So what we ideally want is to check for all the “core.properties” defined
> within all 'instanceDir' paths, which may exist outside the SOLR_HOME dir.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
