Skip to content

InfluxDBRawDataListener misses to insert few rows of data #5654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
asfimport opened this issue Mar 29, 2022 · 3 comments · May be fixed by #5785
Open

InfluxDBRawDataListener misses to insert few rows of data #5654

asfimport opened this issue Mar 29, 2022 · 3 comments · May be fixed by #5785
Milestone

Comments

@asfimport
Copy link
Collaborator

Sandra John (Bug 65981):
We are running a distributed jmeter test for 40 minutes, 8hours & different time configurations.

When the HTML Report is created for jmeter, in that the total number of samples for the 40 minutes test is 284650 but when I queried jmeter table with raw data for the same time period, it showed 207494 samples. ~80000 rows of data seems to be missing.

Can the InfluxDBRawDataListener be tuned to not miss any rows of data to be inserted. The difference increases exponentially with an increase in rampup time.

Severity: normal
OS: Mac OS X 10.1

@vperaltac
Copy link
Contributor

Hello, I encountered this issue as well. Are there any plans to take action on this?

Taking a look at the code for InfluxDBRawBackendListenerClient and InfluxDBBackendListenerClient I noticed that the function teardownTest() includes the following code for InfluxDBBackendListenerClient:

// Send last set of data before ending
log.info("Sending last metrics to InfluxDB");
sendMetrics();

This is not present on InfluxDBRawBackendListenerClient, it just calls:

influxDBMetricsManager.destroy();

@ham1
Copy link
Contributor

ham1 commented Feb 28, 2023

Is it possible to tell if it's the latter metrics that are not being sent? Or could it be other issues e.g. network or influx issues?
If so, please submit a PR do add this to the Raw listener.

@vperaltac vperaltac linked a pull request Mar 6, 2023 that will close this issue
2 tasks
@vperaltac
Copy link
Contributor

@ham1 after some testing, I found that this was not actually the latter metrics not being sent. The issue is, if you have sent multiple requests with the same timestamp, status and transaction values (in general, same tags), InfluxDB will override the previous entry when inserting a new one. I found that this usually happens with the first iteration of requests that Jmeter sends when running multiple threads.

I created a PR for this, there are more details there. (#5785)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants