[
https://issues.apache.org/jira/browse/SOLR-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780103#comment-17780103
]
David Smiley commented on SOLR-16542:
-------------------------------------
The point is to make incremental progress, particularly on an aspect that I
don't think is controversial. Okay?
You make a good point about doing this change in a backwards-compatible way. I
think the client/user perceived result of the scenario you describe is a
failure or timeout; the upload won't happen. Then they will eventually retry
and succeed. I think it's not worth the backwards-compatibility
effort/complexity to have configSet operations be error-free during an in-place
upgrade. There was recent agreement about this for collection restores that
might happen during an upgrade.
> 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]
