[
https://issues.apache.org/jira/browse/SOLR-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622504#comment-13622504
]
Hoss Man commented on SOLR-4663:
--------------------------------
bq. ... The fast fix to the current patch would be just to remove the offending
cores from the lists of cores (both lazily loaded and load-on-startup) and log
an error.
bq. This would imply that when someone tried to actually do something with the
offending cores, they'd get a "core not found" message, which would be slightly
misleading, but there'd be a big fat error (not info, not warn) in the log
files so I'm not too worried. ...
Don't forget that CoreContainer now has the ability to track and report (as
part of "STATUS" requests) that cores failed to initialize (either on startup
or via API calls) and why. (see SOLR-3591 and child tasks)
This type of dataDir error should be no different: if coreA loads fine, and
then coreB fails to load because it points at the same data dir as coreA that
doesn't need to prevent the server from functioning, coreA should still be
usable, and as long as the error is properly recorded in the CoreContainer the
UI and the CoreAdminHandler will report back why coreB isn't available.
> Log an error if more than one core points to the same data dir.
> ---------------------------------------------------------------
>
> Key: SOLR-4663
> URL: https://issues.apache.org/jira/browse/SOLR-4663
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.3, 5.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Attachments: SOLR-4663.patch
>
>
> In large multi-core setups, having mistakes whereby two or more cores point
> to the same data dir seems quite possible. We should at least complain very
> loudly in the logs if this is detected.
> Should be a very straightforward check at core discovery time.
> Is this serious enough to keep Solr from coming up at all?
--
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]
