Why does one server in my cluster have strange CPU/memory stats?
A client asked why one of the three servers in his Solr cluster showed high CPU usage and frequent memory-threshold warnings. SearchStax engineers verified the behavior using the Pulse Monitoring features.
We advised the client that the Java Virtual Machine can behave this way after running for a very long time (JVM "creep"). We advised him to restart the Solr process or to let us restart the server.
Since a SearchStax Solr cluster is configured for high-availabilty, stopping one server temporarily incurs no penalty to query service. The remaining servers pick up the query load until the third server is back on line.
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.