[SOLR-15157] Refactor: separate Collection API commands from Overseer and message handling logic

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 9.0
• Fix Version/s: 9.0
• Component/s: SolrCloud
• Assignee: Ilan Ginzburg
• Reporter: Ilan Ginzburg
• Created: 15/Feb/21 17:09
• Updated: 10/Nov/22 00:58
• Resolved: 10/Nov/22 00:58

Description

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.

Issue Links

• links to: GitHub Pull Request #62
• links to: GitHub Pull Request #2390
• links to: GitHub Pull Request #2410