Closed maxkadel closed 1 month ago
I bumped the memory and CPU (the error seems to suggest this is the problem) on the VM. Could you please test this @maxkadel
I tried testing this and am still seeing the same error (See today's test report).
~I'm going to try prefacing the command with the JVM_ARGS
from @sandbergja's PR to see if they help (JVM_ARGS="-Xms2048m -Xmx2048m"
)~ did not impact this error
We got rid of the error by hitting an individual Solr VM instead of the load-balanced URL, after updating the firewall to allow the private .lib subnet to access the Solr port.
Expected behavior
We can ramp up the number of threads and requests to Solr using JMeter to start hitting Solr-related errors, to see when we are genuinely stressing Solr.
Actual behavior
Before we start getting Solr errors, we get the JMeter error below:
See, for example, the errors on the test run on June 3, 2024
Steps to replicate
Follow the steps in the solr_load_testing README for testing reads.
Impact of this bug
We cannot truly stress the system, making our load tests less meaningful
Implementation notes
I am not actually sure whether the error stems from the loadtest machine or the Solr machine.