[
https://issues.apache.org/jira/browse/SOLR-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker resolved SOLR-12544.
----------------------------------
Resolution: Fixed
I don't think so?I believe the user upgraded to a more recent version and
didn't run into this.
> ZkStateReader can cache deleted collections and never refresh it
> ----------------------------------------------------------------
>
> Key: SOLR-12544
> URL: https://issues.apache.org/jira/browse/SOLR-12544
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.2.1
> Reporter: Varun Thacker
> Priority: Major
>
> After a delete collection call, CLUSTERSTATUS starts breaking with this error
> permanently with this error
> {code:java}
> org.apache.solr.common.SolrException: Error loading config name for
> collection my_collection
> at
> org.apache.solr.common.cloud.ZkStateReader.readConfigName(ZkStateReader.java:198)
> at
> org.apache.solr.handler.admin.ClusterStatus.getClusterStatus(ClusterStatus.java:141)
> ...
> Caused by: org.apache.zookeeper.KeeperException$NoNodeException:
> KeeperErrorCode = NoNode for /collections/my_collection
> ...{code}
> SOLR-10720 addresses the problem by skipping over the collection as it was
> aimed to fix the race condition between delete collection and CLUSTERSTATUS
> being called.
>
> The fact that we see the error never go away , means there is another bug
> lingering which will make the state never refresh and thus other calls list
> LIST will always show the collection.
>
> This happened with Solr 7.2.1 and doesn't happen very often. But when it does
> the only solution is to restart the node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
