[ https://issues.apache.org/jira/browse/SOLR-16542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697750#comment-17697750 ]
Vinayak Hegde commented on SOLR-16542: -------------------------------------- https://issues.apache.org/jira/browse/SOLR-16542?focusedCommentId=17697685&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17697685 sounds like a good idea. Yeah, I think it is going to be too much for me now, I would like to complete this first so that I will have some understanding of the process and the codebase. In the meantime, could you please create a Jira for the next step and share it with me? I will take it up once I have completed this task. > 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) > > > {{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: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org