Giters

satori-com / mzbench

MZ Benchmarking

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

mzbench not connecting to the host specify in the scenario

shaloba opened this issue · comments

commented

Hi,

I have cloned this repository in order to stress test my VerneMQ broker.
I use the following scenario that uses the mqtt_worker from https://github.com/erlio/vmq_mzbench

#!benchDL


#######
# Scenario:
# A single subscriber reading from "prefix/clients/#" topic filter
# 1k publisher publishing to exclusive topic "prefix/clients/{client_id}"
# Overall msg rate: 1k msg/s
# Message size: 150 random bytes
# Running time: 5 min
#######

make_install(git = "https://github.com/shaloba/vmq_mzbench.git",
             branch = "master")

pool(size = 1,
     worker_type = mqtt_worker):

            connect([t(host, "<my-domain>"),
                    t(port,1883),
                    t(client,"subscriber1"),
                    t(clean_session,false),
                    t(keepalive_interval,60),
                    t(proto_version,4), t(reconnect_timeout,4)
                    ])

            wait(1 sec)
            subscribe("prefix/clients/#", 0)

when i run the scenario above I noticed that its not connecting to the host i'm specifying,
I know that its not related to your repo but i'm breaking my brain to figure out this one,
I will appreciate any help!

Thanks in advanced! :)

Shlomy.

commented

Hi, how did you noticed that it is not connecting?
Did you try checking logs?

could you please attach log file except for sensitive parts, it would be helpful for diagnostics

commented

Hi, thanks for the reply.
yes I used also python client to connect the broker and verify it running and everything was Ok.
One more weird thing is that on one of the tests i set the port to 18883 (no service is listening to this one) and still the same result the test ran without failing

this is when using the real port 1883:

log.txt

this one is when I used the fake 18883:

log2.txt

commented

Sorry for late reply, interesting thing is that you have total number of connections (reported by mqtt worker) negative:

"mqtt.connection.current_total",counter,{-1000,

it is probably aware of the problem,
the log you provided is "system log", do you have anything in "user log"?

commented

@parsifal-47
Hello!
I run mqtt_worker test with ssl/tls.
I have same problem, {"mqtt.connection.current_total",counter,{-113,, as bellow

Can you help me to solve the trouble ?

Scenario

#!benchDL

make_install(git = "https://github.com/erlio/vmq_mzbench.git",
             branch = "master")

pool(size = 3,
     worker_type = mqtt_worker,
     worker_start = linear(1 rps)):
            connect([t(host,"my-domain.com"),
                    t(port,8883),
                    t(username,"cred-dev"),
                    t(password, "cred-dev"),
                    t(client,fixed_client_id("mzbench-publisher", worker_id())),
                    t(clean_session,false),
                    t(keepalive_interval,60),
                    t(proto_version,4),
                    t(reconnect_timeout,2)
                    ])
                    
            wait(10 sec)
            set_signal("connect1",1)
            wait_signal("connect1", 3)
            wait(5 sec)
            loop(time = 1 min, rate = 10 rpm):
                publish_to_self("load/test/", random_binary(150), 0)
            disconnect()

Dockerfile
System logs
User logs

commented

Hi Kirill,
my recommendation will be to try MZBench which supports latest OTP version,
https://github.com/mzbench/mzbench
there could be some problems caused by version incompatibility

commented

Thank you for quick reply, i will check.