You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2014/07/19 17:58:39 UTC
[jira] [Comment Edited] (SOLR-5843) No way to clear error state of
a core that doesn't even exist any more
[ https://issues.apache.org/jira/browse/SOLR-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067565#comment-14067565 ]
Shalin Shekhar Mangar edited comment on SOLR-5843 at 7/19/14 3:58 PM:
----------------------------------------------------------------------
I think this is taken care of by SOLR-6232
was (Author: shalinmangar):
I think this is take care of by SOLR-6232
> No way to clear error state of a core that doesn't even exist any more
> ----------------------------------------------------------------------
>
> Key: SOLR-5843
> URL: https://issues.apache.org/jira/browse/SOLR-5843
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.6.1
> Reporter: Nathan Neulinger
> Labels: cloud, failure, initialization
>
> Created collections with missing configs - this is known to create a problem state. Those collections have all since been deleted -- but one of my nodes still insists that there are initialization errors.
> There are no references to those 'failed' cores in any of the cloud tabs, or in ZK, or in the directories on the server itself.
> There should be some easy way to refresh this state or to clear them out without having to restart the instance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org