Why do I see Solr outages and timeouts?
Several users asked for help diagnosing server outages and client connection timeouts.
Client connection timeouts can be due to:
- A fatal error that stops a server. Contact SearchStax support immediately.
- A competing activity that makes Solr temporarily unresponsive to requests.
Check the CPU, Memory, JVM display under Pulse Monitoring. Look for unusually high readings that correspond to the connection problems reported from the field.
- The usual problem is that the system is low on memory. The index may have outgrown the server's RAM. In one instance a high JVM setting led to a massive garbage-collection event that made Solr unresponsive for minutes.
- It is a common error to code in a commit after every update. Very-frequent commits (one every few seconds) place an enormous load on the CPU.
Best Practice Recommendation
A best practice is to use autocommit configuration within Solr Config. This allows many updates to be followed by a single commit.
We love to answer questions!
Please contact the SearchStax Support Desk immediately if you have any question about Solr Cloud deployments.
Return to Frequently Asked Questions.