If your SearchStax Managed Search service Solr system has low performance, out-of-memory errors, or frequent issues with replicas falling into recovery mode, then be sure to read the following helpful topics:
- Is 100% CPU a bad thing? Solr consists of multiple processes competing for CPU time.
- Heartbeat Alerts often appear when Solr is overloaded.
- Solr Out of Memory (OOM): Causes and Solutions: A SearchStax blog on Solr configuration settings that over-allocate memory, which slows down performance and risks crashing Solr.
- CPU Usage alerts can result when the system is under heavy stress.
- System Load Average should be in the single-digit range, but we sometimes see loads of 600 or 800.
- Index Average Response Time / Request alerts occur when index requests take too long.
- Index Error Count alerts are caused by a mismatch between the collection’s schema file and the fields (sometimes values) of the incoming documents.
- Index Timeout alerts mean the system is too overloaded to process /update requests before they time out.
- JVM Heap Used: If the JVM level reaches 100%, Solr will stop, leaving behind an OOM-killer log file.
- Free Disk Space: When a Solr deployment runs out of disk space, it may simply crash. Also, much lower levels of disk usage (below half) can make backups impossible.
- Search – Avg. Response Time/Request: When a query takes minutes to process, it is time to investigate the reason.
- Search Error Count alerts are usually due to query syntax or schema field errors.
- Search Timeout Alerts occur when incoming queries are timing out and failing.
Questions?
Do not hesitate to contact the SearchStax Support Desk.