I will explain the scenario just to avoid all the potential replies asking
why.
We run coldFusion servers (windows) which has SOLR built in (running on
Jetty).
A customer creates a collection which is stored within their own webspace,
they only have read/write access to their own webspace so cannot put them
anywhere else.
the default value for abortOnConfigurationError is true.
This causes endless problems when customers make changes to their websites
or cancel their hosting, the collection gets deleted, and SOLR then crashes
because it cannot find the config files for that collection.
We then have to find out which collection is causing the problem, and
manually remove its entry from solr.xml
Obviously this is a PITA.
In the error output it says.
If you want solr to continue after configuration errors, change:
<abortOnConfigurationError>false</abortOnConfigurationError>
in solr.xml
I have tried this, but it has no effect.
I have also tried putting it in all the solrconfig.xml files
I tried this
<abortOnConfigurationError>${solr.abortOnConfigurationError:false}</abortOnConfigurationError>
and this
<abortOnConfigurationError>false</abortOnConfigurationError>
neither had any effect.
How do you get this to work ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/how-to-get-abortOnConfigurationError-false-working-tp4034149.html
Sent from the Solr - User mailing list archive at Nabble.com.
