[
https://issues.apache.org/jira/browse/SOLR-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709447#comment-17709447
]
Jason Gerlowski commented on SOLR-16542:
----------------------------------------
Well, sure, my question about resources for reading up on DR stuff generally
isn't configset specific. I asked here because getting an overview is helpful
for me or anyone else reviewing this ticket. But fair enough, point taken.
But generally, yep, I know this ticket is configset specific.
bq. I think transitioning ConfigSet processing first is especially low risk
My concern about risk isn't that the operations themselves are particularly
complex. It's that the overseer -> DR switch is a big one for Solr, and we're
turning it on by default for the first time without a workaround in case of
issues. In other words, it's about the framework, not the operations.
bq. Can you describe a scenario in which an async ConfigSet operation would be
useful? [...] a "nice to have" by itself just isn't compelling.
Nothing especially compelling springs to mind, though users@ might know more
than I do. And I'd be curious to see if there was any discussion around when
it was added. But otherwise, definitely a "nice to have" IMO for configset
ops. I wouldn't bat an eye if this ticket removed it for 10.
> 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]
