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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on SOLR-9440:
-------------------------------------------------------

Commit 5982d8734adf44e12cae1985574ca682f07839ca in lucene-solr's branch refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5982d87 ]

SOLR-11076: Added more debug logging. Ensure collections are active before we exercise autoscaling. Added workaround for SOLR-9440.


> 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.7, 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.4.14#64029)

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