[
https://issues.apache.org/jira/browse/SOLR-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925317#comment-13925317
]
Nathan Neulinger commented on SOLR-5843:
----------------------------------------
Two node SolrCloud 4.6.1 deployment.
Do a collection create with a config name that isn't mapped in ZK. You'll get
the initialization failures.
Now - this part is a bit vague - I don't remember the exact cleanup operations
I did - but I think if you go and delete the invalid collection it may or may
not make the errors go away. I thought that in previous cases when I issued the
calls to delete the improperly created collections that it cleaned the errors
up, but it doesn't appear to have in this case. It's possible that one of the
nodes was in a weird state at the time, not sure.
My current situation is I have two nodes, and ONE of them still has the bogus
errors on it, even though all the tabs (and zk tree view) all show no
references to the invalid cores.
beta1_urlDebug_xxxxxxxxx_v16_shard1_replica2:
org.apache.solr.common.cloud.ZooKeeperException:org.apache.solr.common.cloud.ZooKeeperException:
Could not find configName for collection
beta1_urlDebug_xxxxxxxxx_v16_shard1_replica2 found:[c-v17, default]
It's almost like it lost track of the fact that the collection was deleted for
the purpose of the error reporting.
I also can't find ANY reference to that error in the logs currently on the box,
so appears to be in-memory only.
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
