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/27 22:25:45 UTC

[jira] [Created] (SOLR-7985) Solr Overseer Task Management Improvements

Gregory Chanan created SOLR-7985:
------------------------------------

             Summary: Solr Overseer Task Management Improvements
                 Key: SOLR-7985
                 URL: https://issues.apache.org/jira/browse/SOLR-7985
             Project: Solr
          Issue Type: Improvement
          Components: SolrCloud
    Affects Versions: Trunk, 5.4
            Reporter: Gregory Chanan


Capturing some comments/ideas from SOLR-7789 so we don't forget them:

- Can we simplify the OverseerMessageSelector?  There is currently only one implementation of the interface.  Perhaps we can just get rid of the interface
- The processor state is not exposed in a handler-specific way.  That is, there is now a CollectionQueue and a ConfigSetQueue (though they are the same under the covers), but only a single running map, failure map, completed map.  This should probably be combined under a single state object, which would simplify the OverseerTaskProcessor constructor.  Then, we can expose the single state objects for each queue in ZkController.
- The DistributedTaskQueue / OverseerTaskQueue interface is bytes[] based, even though in every case, JSON is passed in.  We should just make the insertion interface JSON based -- this would also allow us to do transformations on insertion because we understand the structure,e.g. an OverseerConfigSetQueue could automatically prefix the action with "configsets:" so we don't expose how the overseer is doing the dispatch under the covers.
- Perhaps we should separate the queue implementation into insertion-only and insertion/removal.  It probably doesn't make sense for the CollectionsHandler / ConfigSetsHandler to be able to remove things from the queue.



--
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