[ https://issues.apache.org/jira/browse/SOLR-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288032#comment-17288032 ]
ASF subversion and git services commented on SOLR-15157: -------------------------------------------------------- Commit c472be5b8687037cf774098e3ac8f9acec48956d in lucene-solr's branch refs/heads/master from Ilan Ginzburg [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c472be5 ] SOLR-15157: fix wrong assumptions on stats returned by Overseer when cluster state updates are distributed (#2410) > Refactor: separate Collection API commands from Overseer and message handling > logic > ----------------------------------------------------------------------------------- > > Key: SOLR-15157 > URL: https://issues.apache.org/jira/browse/SOLR-15157 > Project: Solr > Issue Type: Sub-task > Components: SolrCloud > Affects Versions: master (9.0) > Reporter: Ilan Ginzburg > Assignee: Ilan Ginzburg > Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > Collection API command execution happens in Overseer. The code dealing with > Overseer specific abstractions (Collection API queue management, executing > threads etc) is mixed with code implementing the Collection API commands. > The goal of this ticket is refactoring the Collection API code to abstract > anything that is related to how the Overseer executes the commands, in order > to enable a future ticket (SOLR-15146) to introduce a distributed execution > mode for the Collection API (and keeping the changes limited). > This ticket does not introduce any changes regarding how the Collection API > commands run in the Overseer. It is only refactoring the call chains to allow > a future separation. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org