Multitest has two nodes that are stuck booting

Products

• BlazeMeter

Issue/Introduction

I am trying to run a multitest and two of the GCP Engines are failing to boot. 

Environment

Release :

Component : BLAZEMETER PERFORMANCE TESTING

Cause

In most cases, a misconfigured test, or a test that has not been properly calibrated is the root cause of the Engine hanging during the boot process.

Resolution

1. In the Booting Page, click the Show Engines to see which engines are hung booting. Expand the engine to get the Engine ID. This is the same as the Session ID.
   
   
2. Try stopping the engine by running the following API call:
   https://a.blazemeter.com/api/latest/explorer/#!/sessions/sessionsStop
   
   
3. If the Engine does not stop cleanly, you will need to terminate the session by running:
   https://a.blazemeter.com/api/latest/explorer/#!/sessions/sessionsTerminate

Once the hung sessions have been stopped/terminated, review the test configuration and go through the calibration steps before rerunning the test.

NOTE: The BlazeMeter API Explorer can be found at https://a.blazemeter.com/api/v4/explorer/#/

Additional Information

See:

• https://guide.blazemeter.com/hc/en-us/articles/360000864389-Calibrating-a-Taurus-Test
  
  
• https://guide.blazemeter.com/hc/en-us/articles/360001456978-Calibrating-a-JMeter-Test
  
  
• https://guide.blazemeter.com/hc/en-us/articles/206732959-Calibrating-a-BlazeMeter-test-Legacy-V3-
  
  
• https://guide.blazemeter.com/hc/en-us/articles/207420625-Verifying-your-script-runs-properly-in-BlazeMeter
  
  
• https://guide.blazemeter.com/hc/en-us/articles/360000290058-Engine-Health-Report