[
https://issues.apache.org/jira/browse/SOLR-17877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley reopened SOLR-17877:
---------------------------------
There's a couple bugs here relating to the cluster property (but not EnvUtils
mechanism). One issue is that we really need to parse the cluster property as
a string because it might be a string – likely in practice. Secondly, it's
being read before cluster properties are loaded, which means it's not really
considered at all.
> 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
> Fix For: main (10.0)
>
> Time Spent: 3h 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: [email protected]
For additional commands, e-mail: [email protected]
