-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to shut down? #7
Comments
You can try by doing a kubectl exec into the master pod (in another shell) and use the following command: /jmeter/apache-jmeter-5.0/bin/stoptest.sh |
Thanks! |
You can try by doing a kubectl exec into the master pod (in another shell) and use the following command: above command is run properly but for the next test facing same error again Starting the test @ Thu Jan 05 06:40:50 UTC 2023 (1672900850822) how to fix? |
This happens when the slave pods are still executing a test from the previous command. You need to restart the JMeter server in the slaves for them to start accepting requests from the master |
Following the guide works fine. But when I try to run my own test plan, I get the following:
Engine is busy - please try later Engine is busy - please try later Engine is busy - please try later Engine is busy - please try later Engine is busy - please try later Remote engines have been started Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
How do I shutdown a test?
The text was updated successfully, but these errors were encountered: