[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846208#action_12846208
]
Mark Miller commented on SOLR-1817:
-----------------------------------
1 and 2) I agree - this is part of the big open issue I think is left here -
how to properly deal with abortOnServerConfError. So far I havn't really
dabbled there. Currently, I don't think any of that works in a manner that is
very friendly with Embedded Solr. Its really focused on http - its not great
for tests either.
I do think we should differentiate between the two types of errors as well - in
fact, I think most of the errors where you can still continue still use
SolrConfig.severeErrors because some of them don't have access to the core
name. That is the issue where that possible NPE is - getting access to the core
name. I'm not sure what the right solution for these cases is yet. I think
figuring all this out will help with the issue yonik recently filed as well -
where it will continue if it couldn't load a filter and possibly index
incorrectly. That should be a show stopper error.
3) yes - I agree - it would be great to see a list of the cores that could not
load - then you could click them or something and see the exception page.
> Fix Solr error reporting to work correctly with multicore
> ---------------------------------------------------------
>
> Key: SOLR-1817
> URL: https://issues.apache.org/jira/browse/SOLR-1817
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Mark Miller
> Priority: Minor
> Fix For: 1.5
>
> Attachments: SOLR-1817.patch, SOLR-1817.patch, SOLR-1817.patch
>
>
> Here is a rough patch that attempts to fix how error reporting works with
> multi-core (not in terms of logs, but what you see on an http request).
> The patch is not done - more to consider and havn't worked with how this
> changes solrconfigs abortOnConfigurationError, but the basics are here.
> If you attempt to access the path of a core that could not load, you are
> shown the errors that kept the core from properly loading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
