lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sami Siren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3511) Refactor overseer to use a distributed "work"queue
Date Tue, 05 Jun 2012 13:05:23 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289384#comment-13289384
] 

Sami Siren commented on SOLR-3511:
----------------------------------

bq. but should we leverage this for collection creation as well or will that be a separate
work queue

I think that the same queue could be used easily. The objects that are stored in queue (serialized
in json) are currently specific to core state management and leader announcements but it should
be easy to make that part + the actual processing commands in overseer more general.
                
> Refactor overseer to use a distributed "work"queue
> --------------------------------------------------
>
>                 Key: SOLR-3511
>                 URL: https://issues.apache.org/jira/browse/SOLR-3511
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Sami Siren
>            Assignee: Sami Siren
>         Attachments: SOLR-3511.patch
>
>
> By using a queue overseer becomes a watch free, a lot simpler and probably  less buggy
too.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message