[SOLR-179] Save me from myself! Abort on configuration errors

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2
• Assignee: Ryan McKinley
• Reporter: Ryan McKinley
• Created: 03/Mar/07 23:43
• Updated: 09/Sep/24 18:06
• Resolved: 27/Apr/07 00:04

Description

When something goes wrong in solr configuration, I want solr to stop working and loudly say "something went wrong" This patch adds a collection of severe errors to SolrConfig. If abortOnConfigurationError=true and there are errors, the SolrDispatchFilter prints out a nice message saying "hey something went wrong!"

The specific things that were hidden in error files that will now give dramatic error are:

• unknown class for RequestHandler/ResponseWriter
• any exception throw during handler/writer init()

If you want to disable this behavior (perhaps for a production environment) you need to add:
<abortOnConfigurationError>false</abortOnConfigurationError>
to solrconfig.xml

for more discussion, see:
http://www.nabble.com/merely-a-suggestion%3A-schema.xml-validator-or-better-schema-validation-logging-tf3331929.html

Issue Links

• is related to: SOLR-7199 core loading should succeed irrespective of errors in loading certain components
• is related to: SOLR-17446 The Jetty/Solr process should stop if CoreContainer doesn't initialize