[
https://issues.apache.org/jira/browse/SOLR-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650098#comment-13650098
]
Erick Erickson commented on SOLR-4773:
--------------------------------------
Makes sense, I wasn't altogether happy with the complexification. But we're
leaving the user high and dry when tracking down errors.
Take 4.x and just copy collection1 to collection2 and fire up solr. No warnings
in the log. No errors in the log. But you can't get to collection2, you get a
404 error. And any index mods are done in the collection2 directory.
Admittedly the configuration is foo'd and Solr is doing exactly what the
defined behavior is (identically named cores last one wins). But how the hell
is someone supposed to track that down? Especially with lots of cores? They
don't get a single clue in the place we always say to look, the solr log.
I see where there are tests for creating a core with the same name as an
existing core via the core admin handler, but I don't see at a glance any
coverage for this scenario.
> New discovery mode needs to ensure that instanceDir is correct
> --------------------------------------------------------------
>
> Key: SOLR-4773
> URL: https://issues.apache.org/jira/browse/SOLR-4773
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Affects Versions: 5.0, 4.4
> Reporter: Erick Erickson
> Assignee: Mark Miller
> Fix For: 5.0, 4.4
>
> Attachments: SOLR-4773.patch, SOLR-4773.patch
>
>
> Doing a fresh checkout of 4.x (trunk to to I think) and firing up the example
> fails because we can't find solrconfig. The construction of the instanceDir
> in SolrCoreDiscoverer constructs a path with an extra solr (e.g.
> solr/solr/core).
> I'll attach a patch shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
