You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gregory Chanan (JIRA)" <ji...@apache.org> on 2015/08/01 01:58:04 UTC

[jira] [Created] (SOLR-7855) OverseerCollectionProcessor: separate general task management from collection message handling

Gregory Chanan created SOLR-7855:
------------------------------------

             Summary: OverseerCollectionProcessor: separate general task management from collection message handling
                 Key: SOLR-7855
                 URL: https://issues.apache.org/jira/browse/SOLR-7855
             Project: Solr
          Issue Type: Bug
          Components: SolrCloud
            Reporter: Gregory Chanan
            Assignee: Gregory Chanan


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org