Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-14927 Remove Overseer
  3. SOLR-15157

Refactor: separate Collection API commands from Overseer and message handling logic

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 9.0
    • 9.0
    • SolrCloud
    • None

    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.

      Attachments

        Activity

          People

            ilan Ilan Ginzburg
            ilan Ilan Ginzburg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1.5h
                1.5h