You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alan Woodward (JIRA)" <ji...@apache.org> on 2014/07/08 20:16:06 UTC

[jira] [Resolved] (SOLR-6217) Load cores asynchronously on init

     [ https://issues.apache.org/jira/browse/SOLR-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Woodward resolved SOLR-6217.
---------------------------------

    Resolution: Won't Fix

Too many things in the test suite currently rely on cores being immediately available, and the REST handlers require it as well.  Maybe worth looking at again if we migrate away from SolrDispatchFilter to a standalone HTTP server.

> Load cores asynchronously on init
> ---------------------------------
>
>                 Key: SOLR-6217
>                 URL: https://issues.apache.org/jira/browse/SOLR-6217
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Minor
>         Attachments: SOLR-6217.patch
>
>
> At the moment, we load cores in a threadpool in CoreContainer.init(), but then wait for all cores to load before we register them in ZK and return.  This has two drawbacks:
> 1) SolrDispatchFilter isn't fully initialised until all the cores are loaded, which means that we can still have cores registered in ZK that can't accept HTTP connections
> 2) One slow-loading core will slow down all cores in the node.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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