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

Ramkumar Aiyengar commented on SOLR-7361:
-----------------------------------------

Tim, I understand. What I meant is that we can't currently let through any 
requests because you are not guaranteed that cores will be in a sensible state 
for accepting requests before the core loading threads finish. That's why at 
least the preRegister for all cores needs to finish (and that shouldn't take 
long) before we start accepting requests. Once that happens, I think cores can 
load up in the background (or at least we can try, stumble and fix :) )

> Main Jetty thread blocked by core loading delays HTTP listener from binding 
> if core loading is slow
> ---------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7361
>                 URL: https://issues.apache.org/jira/browse/SOLR-7361
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Timothy Potter
>
> During server startup, the CoreContainer uses an ExecutorService to load 
> cores in multiple back-ground threads but then blocks until cores are loaded, 
> see: CoreContainer#load around line 290 on trunk (invokeAll). From the 
> JavaDoc on that method, we have:
> {quote}
> Executes the given tasks, returning a list of Futures holding their status 
> and results when all complete. Future.isDone() is true for each element of 
> the returned list.
> {quote}
> In other words, this is a blocking call.
> This delays the Jetty HTTP listener from binding and accepting requests until 
> all cores are loaded. Do we need to block the main thread?
> Also, prior to this happening, the node is registered as a live node in ZK, 
> which makes it a candidate for receiving requests from the Overseer, such as 
> to service a create collection request. The problem of course is that the 
> node listed in /live_nodes isn't accepting requests yet. So we either need to 
> unblock the main thread during server loading or maybe wait longer before we 
> register as a live node ... not sure which is the better way forward?



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

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

Reply via email to