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

Yonik Seeley commented on SOLR-3488:
------------------------------------

bq. One thing I recently realized when I put some last minute pieces together 
is that I cannot share the same Overseer queue that already exists - it will 
cause a deadlock as we wait for states to be registered. Processing the queue 
with multiple threads still seemed scary if you were to create a lot of 
collections at once - so it seems just safer to use a different queue.

I'm sure you guys have thought about the command queue more than me at this 
point... but some brainstorming off the top of my head:
- The type of request could implicitly be be synchronous (must complete before 
moving to the next request) or asynchronous
- even for an asynchronous command, the executor for certain types of commands 
could be limited to a single thread to avoid complexity (not sure if that helps 
your deadlock situation or not) 
 
Telling when something is done:
- could have a flag that requests the command be put on a completed queue, 
along with any completion info.
- to prevent unbounded growth of a completed queue, it could have a limited 
size (it could be pretty useful to see a recent history of operations) 

The work queue thing could be a public interface (i.e. external management 
systems could directly make use of it), in which case we'd want to document it 
well eventually.

                
> Create a Collections API for SolrCloud
> --------------------------------------
>
>                 Key: SOLR-3488
>                 URL: https://issues.apache.org/jira/browse/SOLR-3488
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>         Attachments: SOLR-3488.patch, SOLR-3488.patch, SOLR-3488_2.patch
>
>


--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to