[jira] [Commented] (SOLR-9440) ZkStateReader on a client can cache collection state and never refresh it

["Tomás Fernández Löbbe (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015005#comment-16015005 ] 

Tomás Fernández Löbbe commented on SOLR-9440:
---------------------------------------------

I hit this problem all the time in the tests of SOLR-10233, the only workaround I found is to use {{cluster.getSolrClient().getZkStateReader().registerCore(collectionName);}}.

> ZkStateReader on a client can cache collection state and never refresh it
> -------------------------------------------------------------------------
>
>                 Key: SOLR-9440
>                 URL: https://issues.apache.org/jira/browse/SOLR-9440
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>             Fix For: 6.6, master (7.0)
>
>
> I saw this while writing a test case for SOLR-9438. The collection1 collection which was in stateFormat=2 was somehow caching the CloudSolrClient's ZkStateReader such that the returned cluster state contained the collection state. However this collection was neither watched nor lazy so any call to waitForRecoveriesToFinish would see stale state and loop until timeout.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org