[
https://issues.apache.org/jira/browse/SOLR-17877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017347#comment-18017347
]
ASF subversion and git services commented on SOLR-17877:
--------------------------------------------------------
Commit b9be5737969ab614e54abe0f1a23e2fe32e8ec6a in solr's branch
refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b9be5737969 ]
SOLR-17877: fix: don't eagerly fetch DistributedCollectionCommandContext
And we don't need to create yet another instance either; there's already one in
ZkController. DistributedClusterStateUpdater is stateless.
> Create overseerEnabled cluster property
> ---------------------------------------
>
> Key: SOLR-17877
> URL: https://issues.apache.org/jira/browse/SOLR-17877
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Create an "overseerEnabled" cluster property.
> The "distributedClusterStateUpdates" and
> "distributedCollectionConfigSetExecution" in solr.xml cloudConfig shall be
> removed, and instead both behaviors togged with a single boolean setting
> relating to overseer enablement. They weren't documented / advertised.
> If the new cluster property isn't set, we can examine the EnvUtil
> "solr.cloud.overseer.enabled" secondarily. In _another issue_ in Solr 10, a
> third evaluation is done to consider the least Solr version of Solr 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
