1

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?

Dev93
  • 93
  • 2
  • 13

2 Answers2

0

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.

aifrim
  • 555
  • 9
  • 20
neha singhal
  • 1
0

  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
Dmitri T
  • 159,985
  • 5
  • 83
  • 133
  • 1. i have not configured thread to stop when there are errors. 2. i will check the log, have not looked at it. 3. the instances are not run out of memory – Dev93 May 16 '20 at 15:07
  • i tried to restrict the use to just 1 slave from the master. it seems that the problem is because the slow communication between the nodes. the average RPS shows 3-4 requests per second but when runs locally the RPS is 700. is there anything i can do? – Dev93 May 16 '20 at 22:47