Bug 64756 - lost samples when doing distributed testing
Summary: lost samples when doing distributed testing
Status: RESOLVED WORKSFORME
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.3
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: JMETER_5.4
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-21 02:50 UTC by Daniel Qian
Modified: 2020-12-19 12:18 UTC (History)
1 user (show)


Attachments
report (966.61 KB, application/x-bzip2)
2020-09-21 02:51 UTC, Daniel Qian 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Qian 2020-09-21 02:50:14 UTC 
I created a distributed test, prepared 10 remote servers.

A script contains a thread group with 600 threads and 10 loop count.

Theoretically, jmeter should got 600 threads * 10 loop * 10 machine * 9 requests = 540000 samples, but i only got ~ 510000 samples (see attachment)

BTW, if 100 threads, the result is good.
Comment 1 Daniel Qian 2020-09-21 02:51:46 UTC 
Created attachment 37459 [details]
report
Comment 2 Daniel Qian 2020-09-21 03:14:07 UTC 
I found that there is a delay between starting remote engine and remote engine started:

Starting distributed test with remote engines: [jmeter-slave-3.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-7.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-4.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-6.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-5.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-0.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-2.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-8.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-1.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-9.jmeter-slave.jmeter.svc.cluster.local] @ Mon Sep 21 11:09:33 CST 2020 (1600657773078)
summary +      1 in 00:00:00 =    2.9/s Avg:     6 Min:     6 Max:     6 Err:     0 (0.00%) Active: 44 Started: 36 Finished: 0
summary +  16239 in 00:00:25 =  643.0/s Avg:   527 Min:     3 Max:  6832 Err:     0 (0.00%) Active: 2187 Started: 1742 Finished: 74
summary =  16240 in 00:00:26 =  634.4/s Avg:   527 Min:     3 Max:  6832 Err:     0 (0.00%)
summary +  20876 in 00:00:30 =  697.4/s Avg:   624 Min:     3 Max:  7253 Err:     0 (0.00%) Active: 1464 Started: 1822 Finished: 877
summary =  37116 in 00:00:56 =  668.3/s Avg:   582 Min:     3 Max:  7253 Err:     0 (0.00%)
Remote engines have been started:[jmeter-slave-3.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-7.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-4.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-6.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-5.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-0.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-2.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-8.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-1.jmeter-slave.jmeter.svc.cluster.local, jmeter-slave-9.jmeter-slave.jmeter.svc.cluster.local]
Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port 4445
Comment 3 Philippe Mouawad 2020-10-24 15:11:33 UTC 
Can you provide:

- jmeter.Log for controller and workers ?
- the output
- What version of JMeter are you using ? 

Thanks
Comment 4 Philippe Mouawad 2020-12-19 12:18:28 UTC 
Closing as no feedback
Comment 5 The ASF infrastructure team 2022-09-24 20:38:20 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5407