Garbage Collection Pause Cascade
criticalResource ContentionUpdated Mar 19, 2025
Long or frequent garbage collection pauses directly cause query timeouts and latency spikes, particularly when heap usage remains consistently high (>80%), creating a cascading effect on query performance.
Sources
Troubleshooting Solr Slow Queries Using Logs and Metrics - Sematextsematext.com
Solr Out of Memory (OOM): Causes and Solutions | SearchStax Blogwww.searchstax.com
Checklist for troubleshooting performance issues in Solrwww.rajeshkumar.xyz
A Solr performance debugging toolkit - OpenSource Connectionsopensourceconnections.com
How to detect:
Monitor GC frequency, duration, and pause times. Alert when GC pauses exceed query timeout thresholds (typically >500ms). Track heap usage trends - sustained usage above 80% indicates impending GC issues.
Recommended action:
Increase JVM heap size if resources allow. Tune GC settings (e.g., G1GC or ConcMarkSweepGC parameters). Review and optimize cache sizes. Consider horizontal scaling if single-node heap limits are reached.