[
https://issues.apache.org/jira/browse/SOLR-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779828#comment-17779828
]
Ilan Ginzburg commented on SOLR-16542:
--------------------------------------
Unfortunately, the ticket description does not explain the reason we'd want to
switch ConfigSets to distributed mode by code change rather than eventually
switching Collection API + ConfigSet API to distributed mode via existing
configs and then (after a release or so) remove the Overseer supporting code?
Is there a config set related problem that this solves?
The Overseer/queue based API implementation is not compatible with the
distributed implementation. The content of the queues is lost when this change
is made (nothing will consume the queue afterwards), and async calls made
before the change can't be tracked after the change (async tracking is
different as well). This for example does not allow redeploying a cluster node
by node with the config change (the cluster must be stopped completely, then
config changed then restart, and everything in the queue at this point is
lost). This means a cluster can't be redeployed node by node with the code
change suggested in this ticket.
> Remove OverseerConfigSetMessageHandler; always do distributed mode
> ------------------------------------------------------------------
>
> Key: SOLR-16542
> URL: https://issues.apache.org/jira/browse/SOLR-16542
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Major
> Labels: newdev
> Fix For: main (10.0)
>
> Attachments: output5.log, output6.log
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> {{distributedCollectionConfigSetExecution}} is a boolean setting on
> solr.xml/solrCloud that switches *both* Collection API *and* ConfigSet API
> processing between Overseer based (when =false) vs distributed (when =true).
> In this issue, remove the Overseer based processing of ConfigSets, thus
> always use DistributedCollectionConfigSetCommandRunner instead for ConfigSet
> processing, regardless of the {{distributedCollectionConfigSetExecution}}
> boolean setting. Namely, OverseerConfigSetMessageHandler would be removed.
> The boolean toggle would henceforth only toggle the "collection" aspect of
> wether to do distributed processing vs Overseer (centralized).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
