[SOLR-4011] SolrCore - correct behavior while having error loading specific cores

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Not A Problem
• Component/s: multicore

Environment

RHEL 6.1/6.3

Solr 3.6.1

• Assignee: Erick Erickson
• Reporter: Gianluca Varisco
• Created: 29/Oct/12 11:10
• Updated: 29/Oct/12 14:19
• Resolved: 29/Oct/12 14:19

Description

I've a multicore setup. Solr.xml contains the following:

<solr persistent="false">

<!--
adminPath: RequestHandler path to manage cores.
If 'null' (or absent), cores will not be manageable via request handler
-->
<cores adminPath="/admin/cores">
<core name="a" instanceDir="/shop/www/htdocs/a/shop.staging/solr/app" dataDir="/shop/solr/staging/a/data/" configName="solrconfig.xml" schemaName="schema.xml" />
<core name="b" instanceDir="/shop/www/htdocs/b/shop.staging/solr/app" dataDir="/shop/solr/staging/b/data/" configName="solrconfig.xml" schemaName="schema.xml" />
<core name="c" instanceDir="/shop/www/htdocs/c/shop.staging/solr/app" dataDir="/shop/solr/staging/c/data/" configName="solrconfig.xml" schemaName="schema.xml" />
</cores>
</solr>

When solr starts, it tries to LOAD all the cores. If one fails (no solrconfig.xml or instanceDir found), the whole multicore configuration is broken and Solr won't answer as well for the other two cores.

Is there a workaround for it? Reasons while it can happen is, for example, if cores' creation in the XML are managed indipendently (e.g via Puppet) but applications are not deployed in that instanceDir yet (therefore: no solrconfig.xml/schema.xml). Is there a specific parameter to use?