Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-7855

OverseerCollectionProcessor: separate general task management from collection message handling

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4, 6.0
    • Component/s: SolrCloud
    • Labels:
      None

      Description

      While working on SOLR-7789, I realized it would be easier if I split up the OverseerCollectionProcessor into two parts:

      1) General handling of tasks (work queues, etc)
      2) Processing a collection handler request

      I haven't decided whether the ConfigSet should have its own processor, i.e. OverseerConfigSetProcessor or reuse at least the thread for the OverseerCollectionProcessor, but in either case this refactoring will be helpful. That is, if the ConfigSet processing has its own processing, I can reuse the general handling of tasks part. If the ConfigSet processing reuses the OverseerCollectionProcessing thread, I won't complicate the implementation with ConfigSet operations.

        Attachments

        1. SOLR-7855.patch
          284 kB
          Gregory Chanan
        2. SOLR-7855.patch
          301 kB
          Gregory Chanan
        3. SOLR-7855.patch
          305 kB
          Gregory Chanan

          Issue Links

            Activity

              People

              • Assignee:
                gchanan Gregory Chanan
                Reporter:
                gchanan Gregory Chanan
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: