[SOLR-6265] core errors on startup are not showing up in the log until attempts to use the core?

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 4.10, 6.0
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 21/Jul/14 23:57
• Updated: 09/May/16 18:52
• Resolved: 23/Jul/14 17:51

Description

As of r1612418, both the 4x and trunk svn trees seem to have a bug where any core specific init errors that occur on startup don't show up in the log until/unless someone attempts to access that core via HTTP.

i'm not sure when exactly this bug was introduced, but it definitely isn't in 4.9.

The impact on users, particularly new users, is that starting up solr with a mistake in your configs appears to work fine until you actually try to use solr and then you get ugly errors.

Issue Links

• is part of: SOLR-6232 Allow cores that have failed to init to be deleted via CoreAdminHandler