[
https://issues.apache.org/jira/browse/SOLR-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069587#comment-14069587
]
Erick Erickson commented on SOLR-6265:
--------------------------------------
Any chance this is specified as a "lazily loaded" core? In that case this would
be expected behavior....
Unlikely to be the problem, but I thought I'd ask to be sure.
> core errors on startup are not showing up in the log until attempts to use
> the core?
> ------------------------------------------------------------------------------------
>
> Key: SOLR-6265
> URL: https://issues.apache.org/jira/browse/SOLR-6265
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Priority: Blocker
> Fix For: 4.10
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
