Ran a JDBC load test with heavy queries which take up to 80,000 ms to return. The test is shaped with the "jp@gc - Ultimate Thread Group" for five minutes:
As the test runs I noticed that the data as seen in Grafana is cuttof during the hold time and it was at the 5 minutes interval. It seems the bug is that it should allow to continue writing to InfluxDB even though some threads are lagging behind because of long response time:
JMeter 5.0
Ran a JDBC load test with heavy queries which take up to 80,000 ms to return. The test is shaped with the "jp@gc - Ultimate Thread Group" for five minutes:
As the test runs I noticed that the data as seen in Grafana is cuttof during the hold time and it was at the 5 minutes interval. It seems the bug is that it should allow to continue writing to InfluxDB even though some threads are lagging behind because of long response time: