lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Thacker (JIRA)" <>
Subject [jira] [Resolved] (SOLR-12544) ZkStateReader can cache deleted collections and never refresh it
Date Tue, 08 Jan 2019 19:15:00 GMT


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

> ZkStateReader can cache deleted collections and never refresh it
> ----------------------------------------------------------------
>                 Key: SOLR-12544
>                 URL:
>             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
>     at org.apache.solr.handler.admin.ClusterStatus.getClusterStatus(
> ...
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message