[
https://issues.apache.org/jira/browse/SOLR-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709164#comment-17709164
]
David Smiley commented on SOLR-16542:
-------------------------------------
Jason, I _think_ you are coming at this more broadly but this JIRA issue is
very specific to ConfigSet handling. The parent issue would be where to ask
the broad question (e.g. DistributedRunner) and maybe at-mention Ilan. "async"
here is specific to ConfigSets. I think transitioning ConfigSet processing
first is especially low risk. I wish it was never done on the Overseer to
begin with; never made sense to me.
Can you describe a scenario in which an async ConfigSet operation would be
useful? There is a complexity/implementation cost to everything, so a "nice to
have" by itself just isn't compelling.
> 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 10m
> 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]
