jmeter distributed testing slave finishes before schedule

1
votes

i have a jmeter distributed system with 1 master and 4 slaves.

the test is configured to run for 60 minutes. somehow suddenly a random slave finish the test and the load is distributed between the other 3. all the slaves configured the same way.

the instances are aws ec2 instances on the same subnet

is there any explanation for this behaviour?

2
jmeterjmeter-5.0distributed-testing

2 Answers

0
votes

  1. It might be the case you configured JMeter to stop thread when the error occurs yourself:

    enter image description here

    if you have marked settings under Thread Group it might be the case the Threads (virtual users) are being stopped or the whole test gets stopped on error

  2. If unexpected error occurs there should be a corresponding entry in jmeter.log file, make sure to execute JMeter slave process providing log file location via -j command-line argument like:

     ./jmeter -s -j jmeter-slave.log .....

  3. It might be the case your JMeter instance runs out of memory and the whole JVM gets terminated so make sure to properly tune it for high loads

  4. Check operating system log of your Amazon instance
0
votes

There could be multiple reason for it:

  1. Possibly load balancing was not happening properly, more sets of request are getting drived toward one instance. That can cause the VM to crash
  2. OR It could be the crashed AWS instance. The disk space got full.

I suggest you check the disk usage of crashed vm.