Which checks are relevant?

[tokee]

As @DmitryKey points out in #1, extending the script to check for errors that Solr also catches would increase its value as a validator as part of deployment. The question is which checks would make sense?

Some seems non-controversial:

• Validate the XML (xmllint)
• Check for valid values in attributes
• Check for all mandatory attributes being present

Less simple is sanity checking:

• Very low auto commit values
• Very high auto warm count
• Very high max rows

Suggestions and thoughts welcome.

[DmitryKey]

While thinking about the answer to the question, I got to think about deployment process. If the validator tool would provide reasonable interface in a form of return codes / messages, it could be useful for making such operations as rollback of the deployed components.

One idea, that comes to mind on what to check (might not be too easy / generalizable) is to read the plugin class(es) from solrconfig.xml and look into collection's / core's lib directories to make sure there is such a class in one of the binaries.

query_plugin_class=<get the plugin class>
clazz = $(jar tvf collection/lib/*.jar | grep $query_plugin_class)
# check that clazz is not empty, otherwise report a warning