[
https://issues.apache.org/jira/browse/SOLR-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007973#comment-18007973
]
David Smiley commented on SOLR-17293:
-------------------------------------
With SOLR-17664 (now linked as required), we can see if a cluster has been
created under Solr 10, and simply change the default for new clusters. An
existing cluster can be changed safely by shutting down completely then
starting with the setting enabled. A rolling upgrade isn't a safe method here.
As we have other cluster properties for cluster level settings, I think it
makes loads of sense for this non-Overseer/distributed mode to also have a
cluster property, because it's definitely a cluster centric setting (not node).
Either the cluster operates in this mode, or it doesn't; it's not for any one
node to decide based on its version or anything.
> 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: Major
>
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
