JMeter distributed on ec2

[Paul Spehar]

I have Taurus setup and working on a second host (amazon linux ec2).  When I run taurus on my first host, I see a Connection Refused in jmeter log from the slave.

2017/03/28 21:59:27 ERROR - jmeter.engine.DistributedRunner: Failed to create engine at 10.112.96.165 java.rmi.ConnectException: Connection refused to host: 10.112.96.165; nested exception is: 

        java.net.ConnectException: Connection refused (Connection refused)

So I logged into the slave, edited jmeter-server RMI_HOST_DEF to include the internal IP of the slave, and started jmeter-server process.  This is the same thing I would have done to prepare an ec2 slave to run in JMeter distributed mode without TAURUS.

And it worked.  But is this the expected process to prepare a slave for TAURUS?  

One other question surrounding distributed mode: 

Is distributed mode supported by dockerized TAURUS?

[Andrey Pokhilko]

Hi,

Your question is about JMeter, not about Taurus. Taurus just runs JMeter. The jmeter-server functioning is out of scope for Taurus, the purpose of Taurus is different.

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/83101f1e-b5fb-47a4-b18f-e5756c588db7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Paul Spehar]

Let me rephrase. When using taurus to execute jmeter tests in distributed mode, other than installing taurus, what are the preparation steps required on the distributed servers?

[Andrey Pokhilko]

I don't know any other preparation steps. You just install Taurus, then run it.

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

[Paul Spehar]

Maybe I am misunderstanding. 

I just tried this process out on a fresh install and came up with the following in the jmeter.log where I tried to kick off bzt from x.x.x.111:

2017/03/29 23:50:12 ERROR - jmeter.engine.DistributedRunner: Failed to create engine at x.x.x.180 java.rmi.ConnectException: Connection refused to host: x.x.x.180; nested exception is: 

        java.net.ConnectException: Connection refused (Connection refused)

        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)

This is how I am pointing to x.x.x.180 in my yml that is being run from x.x.x.111: 

execution:

- distributed:

  - x.x.x.180

  concurrency: 10000

  throughput: 1000

  ramp-up: 10m

  hold-for: 10m

  scenario: variant

On x.x.x.180, to prepare I have installed bzt and confirmed it works by running a simple smoke test involving JMeter.  Running that smoke test downloaded JMeter as expected:

ubuntu@ip-x-x-x-180:/tmp/my-test$ bzt quick_test.yml 

23:55:26 INFO: Taurus CLI Tool v1.8.4

23:55:26 INFO: Starting with configs: ['quick_test.yml']

23:55:26 INFO: Configuring...

23:55:26 INFO: No personal config: /home/ubuntu/.bzt-rc

23:55:26 INFO: Artifacts dir: /tmp/my-test/2017-03-29_23-55-26.962724

23:55:26 INFO: Preparing...

23:55:27 INFO: Will install JMeter into /home/ubuntu/.bzt/jmeter-taurus

23:55:27 INFO: Downloading: https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-3.1.zip

100% [===============================================================================================================================================================================================================================] Time: 0:00:04

23:55:32 INFO: Unzipping /tmp/tmpr0Y9M4.zip to /home/ubuntu/.bzt/jmeter-taurus

23:55:37 INFO: Downloading jmeter-plugins-manager-0.12.jar from https://search.maven.org/remotecontent?filepath=kg/apc/jmeter-plugins-manager/0.12/jmeter-plugins-manager-0.12.jar                                                  ] ETA:  --:--:--

23:55:38 INFO: Downloading cmdrunner-2.0.jar from https://search.maven.org/remotecontent?filepath=kg/apc/cmdrunner/2.0/cmdrunner-2.0.jar=============================================================================================] ETA:  0:00:00

100% [===============================================================================================================================================================================================================================] Time: 0:00:01

23:55:39 INFO: Installing JMeter plugins: jpgc-casutg,jpgc-dummy,jpgc-ffw,jpgc-fifo,jpgc-functions,jpgc-json,jpgc-perfmon,jpgc-prmctl,jpgc-tst

23:55:46 INFO: Starting...

23:55:46 INFO: Waiting for results...

23:55:46 INFO: Waiting for finish...

23:57:22 WARNING: Please wait for graceful shutdown...

23:57:22 INFO: Shutting down...

23:57:22 INFO: Post-processing...

23:57:22 INFO: Test duration: 0:01:36

23:57:22 INFO: Samples count: 81, 0.00% failures

23:57:22 INFO: Average times: total 0.013, latency 0.013, connect 0.000

23:57:22 INFO: Percentile 0.0%: 0.002

23:57:22 INFO: Percentile 50.0%: 0.005

23:57:22 INFO: Percentile 90.0%: 0.009

23:57:22 INFO: Percentile 95.0%: 0.011

23:57:22 INFO: Percentile 99.0%: 0.436

23:57:22 INFO: Percentile 99.9%: 0.436

23:57:22 INFO: Percentile 100.0%: 0.436

23:57:22 INFO: Artifacts dir: /tmp/my-test/2017-03-29_23-55-26.962724

23:57:22 INFO: Done performing with code: 0

So what else would be needed to get x.x.x.180 to participate as part of a distributed test?

[Andrey Pokhilko]

On your slave, you need to start jmeter-server. This is done outside Taurus, read here: http://jmeter.apache.org/usermanual/remote-test.html

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/78b5c8f7-4496-4da3-9dd0-6ffa7e7b57cf%40googlegroups.com.