You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2015/03/16 20:08:39 UTC
[jira] [Comment Edited] (SOLR-7199) core loading should succeed
irrespective of errors in loading certain components
[ https://issues.apache.org/jira/browse/SOLR-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363727#comment-14363727 ]
Noble Paul edited comment on SOLR-7199 at 3/16/15 7:08 PM:
-----------------------------------------------------------
OK , hold your horses. We discussed the problem and I'll put up a new description and proposed solution and why we need this
was (Author: noble.paul):
OK , hold your horses. We discussed and I'll put up a new description and proposed solution and why we need this
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org