Endurance Testing using jmeter stopped abruptly in distributed environment

**Amit Agrawal** ([Bug 65213](https://bz.apache.org/bugzilla//show_bug.cgi?id=65213&redirect=false)):
I am using Azure Kubernetes Service(AKS) to deploy JMeter infrastructure. Using JMeter - 5.2.1 version and Kubernetes version - 1.19.6.

I am running 24 hrs endurance test using JMeter with ThroughputShapingTimer. My test stopped abruptly some time after 6 hrs and some time 8 hrs.

I checked jmeter-server.log file and getting warning - WARN k.a.j.t.VariableThroughputTimer: No free threads left in worker pool.
No error observed in jmeter.log from jmeter slave.

I used 400 threads and then 800 threads and then tried 1100 threads still getting - No free threads left in worker pool.

I increased jmeter slave and master memory from 2GB to 6GB and 4 cores of CPU still issue persists.

I checked kubernetes PODS, they were not restarted so assuming there is Out of Memory concern.
I ran with 2 slaves and 1 master also.

Please advise how to overcome this issue.

Following attachments are provided.
1. Test Plan
2. Jmeter-server.log file.

Votes in Bugzilla: 1
Severity: critical
OS: Linux