[
https://issues.apache.org/jira/browse/SOLR-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363717#comment-14363717
]
Erick Erickson commented on SOLR-7199:
--------------------------------------
-1 as well. "fail early fail often" is a good motto here. Now for any one of a
number of errors I don't know anything's wrong until a query happens to hit.
Which may not happen for hours/days/whatever. Now I have to go back to the logs
and try to figure out what went wrong... which may have rolled over.
I could deal with letting people specify they don't care whether a particular
component loads or not, but I'm lukewarm to that as well for the most part.
This seems like a cure worse than the disease. Rather than have the core come
up anyway, what about some kind of supervisory code that _will_ come up
independent of cores to handle this use-case (I admit I really haven't looked
into the details though, possibly this is a nonsensical idea).
> core loading should succeed irrespective of errors in loading certain
> components
> --------------------------------------------------------------------------------
>
> Key: SOLR-7199
> URL: https://issues.apache.org/jira/browse/SOLR-7199
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Attachments: SOLR-7199.patch
>
>
> If a certain component has some error , the core fails to load completely.
> This was fine in standalone mode. We could always restart the node after
> making corrections. In SolrCloud, the collection is totally gone and there is
> no way to resurrect it using any commands . If the core is loaded , I can at
> least use config commands to correct those mistakes .
> In short, Solr should try to make the best effort to make the core available
> with whatever components available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
