lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Resolved] (SOLR-1817) Fix Solr error reporting to work correctly with multicore
Date Fri, 07 Sep 2012 21:52:08 GMT


Hoss Man resolved SOLR-1817.

    Resolution: Fixed

this issue languished for a long time, but i'm resolving as "fixed" in 4.0 since there have
been a lot of improvements since the last time anyone looked at this jira in terms of how
multicore erors are handled...

1) aboutonConfigError no longer even exists
2) solr can now start up and server some cores even if other cores fail
3) CoreAdminHandler and the admin UI can now display errors about cores that failed to init
- either on startup, or because of an explicit CREATE/RELOAD request

> Fix Solr error reporting to work correctly with multicore
> ---------------------------------------------------------
>                 Key: SOLR-1817
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Mark Miller
>            Priority: Minor
>             Fix For: 4.0
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message