Long running (soak) test ending prematurely

Products

• BlazeMeter

Issue/Introduction

Long running tests may end before the configured duration. The logs may explain what happened but what if no artifacts.zip or admin-artifacts.zip are present?

Environment

BLAZEMETER PERFORMANCE TESTING

Cause

Situations like these are often caused by lack of disk space. Long running test cause much information to be written to the load generators and can cause the hard disk (in particular the file system mapped to the /tmp dir) to fill up after several hours/days. This may be especially evident if the test runs on multiple engines and one engine stops before the other, like can be seen in this test:

Resolution

If the engines are located in private locations, rerun the test and monitor the available free space with a periodic 'df -h' commands on the agents that the test runs on. It will tell you if disk space decreases and how fast.

It allows you to determine if the disk space needs to be increased in order for a future test to run through its configured duration.