[
https://issues.apache.org/jira/browse/SOLR-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680780#comment-14680780
]
Scott Blum commented on SOLR-6629:
----------------------------------
Note: LegacyClusterStateWatcher.refreshAndWatch() is what currently triggers
refreshLazyFormat2Collections(). In other words, refreshes on the lazy
collection set are tied to changes in shared clusterstate.json. A better
solution would be to do a child watch on /collections instead and completely
decouple the lazy collection set from changes to clusterstate.json. This might
also involve tracking down any overseer code that forces a now-unnecessary
clusterstate.json mutation purely as a signal.
> Watch /collections zk node on all nodes
> ---------------------------------------
>
> Key: SOLR-6629
> URL: https://issues.apache.org/jira/browse/SOLR-6629
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Fix For: Trunk
>
>
> The main clusterstate.json is refreshed/used as a poor substitute for
> informing all nodes about new or deleted collections even when the collection
> being created or deleted has state format > 1. When we move away from state
> format 1 then we should do away with this workaround and start watching the
> /collections zk node on all nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
