[
https://issues.apache.org/jira/browse/SOLR-17946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126875#comment-18126875
]
David Smiley commented on SOLR-17946:
-------------------------------------
If each node has node roles set –
{{SOLR_NODE_ROLES="data:on,overseer:disallowed"}} disallowing the overseer,
then I suspect there are no such queues. What we should probably do is have
the overseer disablement imply a change of default of the overseer node role.
> Disabled Overseer shouldn't create ZK queues.
> ---------------------------------------------
>
> Key: SOLR-17946
> URL: https://issues.apache.org/jira/browse/SOLR-17946
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 10.0
> Reporter: David Smiley
> Priority: Major
>
> When the Overseer is disabled, internally we create an Overseer and elect it
> _anyway_ because of the cluster singleton mechanism which is tied to the
> Overseer. Unfortunately, the Overseer forcibly creates seven ZK queues /
> maps under the "/overseer/" zk path such as "/overseer/queue",
> "/overseer/queue-work", "/overseer/collection-map-running" and more. +We
> should prevent this from happening when the Overseer is disabled.+
> The Overseer election path at "/overseer_elect" is separate and would stay.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
