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

Shalin Shekhar Mangar commented on SOLR-9014:
---------------------------------------------

bq. Yes, unfortunately. ClusterState.collectionStates is driven (in part) by 
/solr/collections/<children>. In particular, if /solr/collections/foo exists, 
the foo collection is not being watched, and /solr/collections/foo/state.json 
does NOT exist, then the collection will appear in collectionStates as a 
LazyCollectionRef, but it won't resolve to a DocCollection since there's no 
state.json. We don't poll or watch for the existence of the state.json for 
non-watched collections.

This is what I don't understand. If /solr/collections/foo exists, won't the 
collection exist either in legacy clusterstate.json or in 
/solr/collections/foo/state.json? Granted that there is an edge case where a 
collection might be under construction but otherwise this should hold true? So 
if the goal is to return a Set of names of collections, why must we try to 
resolve each entry in ClusterState.collectionStates?

> Deprecate and reduce usage of ClusterState methods which may make calls to ZK 
> via the lazy collection reference
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-9014
>                 URL: https://issues.apache.org/jira/browse/SOLR-9014
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>             Fix For: master, 6.1
>
>         Attachments: SOLR-9014.patch
>
>
> ClusterState has a bunch of methods such as getSlice and getReplica which 
> internally call getCollectionOrNull that ends up making a call to ZK via the 
> lazy collection reference. Many classes use these methods even though a 
> DocCollection object is available. In such cases, multiple redundant calls to 
> ZooKeeper can happen if the collection is not watched locally. This is 
> especially true for Overseer classes which operate on all collections.
> We should audit all usages of these methods and replace them with calls to 
> appropriate DocCollection methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to