lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3591) Startup error not reflected in Solr web view
Date Tue, 10 Jul 2012 23:35:34 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411059#comment-13411059
] 

Hoss Man commented on SOLR-3591:
--------------------------------

bq. Perhaps we can use part of SOLR-3358 to capture FATAL exceptions and somehow expose them
regardless of the core?

i don't have any objections to that, what i've seen of SOLR-3358 looks great so far, and it
would be nice if it was accesible even w/o having any SolrCores -- but i think we need a more
specific targeted solution for reporting core initialization problems...

* we can't uniquely identify which core caused which log messages
* we can't control what log messages might come out of a plugin from a core
* we can't identify which log message was the "straw that broke the camels back" and actually
caused the core init to fail.
* we can't definitively know if a log message is "still important" as more log messages come
in (from other cores)
* we can't know if a specific log messages related to core initialization is "still a problem"
or if that specific core has already been fix and re-created

...but we can, in CoreContainer, catch and record the specific exceptions related to each
core name, and track them relative that core name, and let CoreAdminHandler have thta data
when it's asked to report status.

so if a plugin in coreA logged 99 "fatal" log messages, but coreA still started fine; while
coreB didn't log anything but the constructor threw an exception X we can make CoreAdminHAndler
reliably (and confidently) say "here's your status for coreA, and FYI: coreB failed to initialize
because of X" w/o making the user wade through 100 other log messages that are unrelated.
 And even if the user doesn't look at the core status for hours and hours after trying to
startup (or after some cron tried to programaticly create coreB), and there have been thousands
of other "errors" logged by other cores, CoreAdminHandler can still say "this error X is the
reason you don't have a coreB right now".

see what i mean?

                
> Startup error not reflected in Solr web view
> --------------------------------------------
>
>                 Key: SOLR-3591
>                 URL: https://issues.apache.org/jira/browse/SOLR-3591
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 4.0-ALPHA
>            Reporter: Erik Hatcher
>            Assignee: Stefan Matheis (steffkes)
>            Priority: Blocker
>             Fix For: 4.0
>
>         Attachments: screenshot-1.jpg
>
>
> When Solr has a fatal startup error, it used to be reflected in general responses from
Solr.  With the new UI, it's relegated to only the logs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message