[
https://issues.apache.org/jira/browse/SOLR-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028468#comment-18028468
]
Ilan Ginzburg commented on SOLR-17293:
--------------------------------------
There's the need to tell an Overseer (even if it only does cluster singleton
management) to quit. This requires a queue.
If the queues ZooKeeper directory presence is used as a flag, these directories
need to be deleted at some point.
Is the current cluster configuration written somewhere in ZooKeeper that can be
read by SolrJ clients (which I assume is the motivation here?)
> Umbrella: Decentralized Cluster Processing as default
> -----------------------------------------------------
>
> Key: SOLR-17293
> URL: https://issues.apache.org/jira/browse/SOLR-17293
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Blocker
> Labels: pull-request-available
> Fix For: main (10.0)
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This is an umbrella issue for tracking work required for running SolrCloud
> with two booleans as default: {{distributedClusterStateUpdates}} and
> {{distributedCollectionConfigSetExecution}}, which we may rename/refactor
> (TBD). When they are set, the Overseer has nothing to do except run "Cluster
> Singleton Plugins" (if you configure any).
> These have been in Solr for years since well before 9.0 and are tested in a
> randomized fashion. But they have not experienced real-world usage to our
> knowledge. There are some scalability concerns, and unclear compatibility
> with PRS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
