Hi,

We have set <abortOnConfigurationError>false</abortOnConfigurationError> in
solrconfig.xml for all the cores but still whenever any configuration error
occurs search does not work in any of the cores. Is there any other
configuration we have to set so as to not affect search in the cores which
are configured correctly?

For one of the core, we got following error today but then none of the core
is working after that. The below message suggests to add
abortOnConfigurationError in solr.xml but we have it added in solrconfig.xml
for all the cores. Do we need to add in solr.xml? If yes, where?

Please suggest what is the right way to configure so that if one core fails
due to configuration errors, all other cores remain unaffected?

*****************************************************************
Check your log files for more detailed information on what may be wrong.

If you want solr to continue after configuration errors, change: 

 &lt;abortOnConfigurationError&gt;false&lt;/abortOnConfigurationError&gt;

in solr.xml

java.lang.RuntimeException: java.io.IOException: Cannot create directory:
/usr/local/app/data/search/core09/index
***********************************************************************
-- 
View this message in context: 
http://www.nabble.com/abortOnConfigurationError%3Dfalse-not-taking-the-effect-in-solr-1.3-tp25332254p25332254.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to