apache
Issue in running Distributed runs using Jmeter
Chandrakumar Sekar (Bug 65874): Hello Team,
Im raising an issue to seek your support and help in executing a Remote distributed runs using Jmeter. Following are the details of the issue and Test VM's that I currently use for Remote distributed runs.
Test VM details: Machine OS: Windows 2019 Server edition. Machine configuration: 4 Core CPU and 16 GB RAM. These machines are restricted across network interms of Firewall. All machines are having same IP subnet 10.135.159.*
Tool Details: Jmeter Version: 5.4.1 with updated log4j version. Java version: 1.8 on all machines Placed all scripts and data files on same path as of Master machine
Jmeter Configuration details: As machines are restricted across network, I have opened Firewall between the machines on port 1099 for the purpose of remote distributed runs. Hence, accordingly the Jmeter properties are updated with below details.
Jmeter.properties updated as follows, remote_hosts = Machine IP which i planned to use as remote agents (slave) server.rmi.port=1099 server.rmi.local.port=1099
As machine is blocked with firewall restrictions, opened a port 1099 on machines for remote distributed runs.
Observations:
- Started Jmeter-server.bat on slaves. it started with no exceptions or errors and on the port 1099 as defined in properties file.
- Jmx was scheduled to run for 2 mins as a validation for Remote distributed runs.
- Started a jmx using command file jmeter -n -t "Path of Jmx" -R 10.135.159.1,10.135.159.2
- received a message on slave Jmeter server window that started test at Timestamp.
As an expected result: the given userload should execute on all slaves and Jmeter metrics should reflect in Grafana Dashbaord as wel. However its showing user count and TPS as not appropriate, i.e. Request per second graph was updating on periodic intervals with request counts, also same is being observed in the aggregate report listener on Jmeter GUI window.
Additionally, at the end of the run observed slave got the finished message after 3 mins from scheduled run time of Jmx file.
could you please review the provided details and advise us on this behaviour what is blocking us in executing a remote distributed runs on above said machines?
Thanks in advance, Chandrakumar Sekar.
Severity: major OS: All
Chandrakumar Sekar (migrated from Bugzilla): Further, when going through the Jmeter user Manual it also mentioned that we need to specify the port for client as well. i.e. client.rmi.localport in jmeter.properties file. hence after making this change, now im getting run executed with no delays in start and finish times, thread count as well immediately reflecting in Jmeter aggregate report and Grafana panels. However TPS rate/number of samplers is still appearing to be issue which is updating with delays and need your support to understand if any port to be updated in jmeter properties.
Current Jmeter.property file update: (windows machine) server_port=1099 server.rmi.port=1099 server.rmi.localport=1099 client.rmi.localport=19201 (on Controller machine only).
@pmouawad (migrated from Bugzilla): Hello, Please ask on user mailing list:
https://jmeter.apache.org/mail2.html
And provide at least:
- jmeter.log of each server
- The JMX file
- Expected throughput vs obtained one
Also please read:
- https://jmeter.apache.org/usermanual/remote-test.html
- https://jmeter.apache.org/usermanual/properties_reference.html#remote
- https://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.html
Thank you Regards