[
https://issues.apache.org/jira/browse/SOLR-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903977#comment-17903977
]
David Smiley commented on SOLR-6629:
------------------------------------
A voice from the future and from a fork of SolrCloud: It's not necessary that
any node watch for collections coming into (or out of) existence. It doesn't
scale with high collection counts, and it adds complexity as well.
> 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: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 5.4, 6.0
>
> Attachments: SOLR-6629-new.patch, SOLR-6629.patch, SOLR-6629.patch,
> SOLR-6629.patch, SOLR-6629.patch, SOLR-6629.patch
>
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
