search

vernemq / vmq_mzbench

An MQTT loadtest and usage scenario tool for VerneMQ and other MQTT systems.
Apache License 2.0
42 stars 45 forks source link

Dynamic deadlock detected for 1_to_1 scenario #19

Closed eckucukoglu closed 6 years ago

eckucukoglu commented 6 years ago

When I try to run 1_to_1 scenario, I receive dynamic deadlock detected error:

09:51:58.603 [error] [ API ] <0.4582.0> Benchmark result: FAILED
Dynamic deadlock detected

09:51:58.618 [error] [ API ] <0.4548.0> Stage 'pipeline - running': failed
Benchmark has failed on running with reason:
{benchmark_failed,{asserts_failed,1}}

Stacktrace: [{mzb_pipeline,error,2,
                           [{file,"/home/test/mzbench/server/_build/default/deps/mzbench_api/src/mzb_pipeline.erl"},
                            {line,90}]},
             {mzb_pipeline,'-handle_cast/2-fun-0-',6,
                           [{file,"/home/test/mzbench/server/_build/default/deps/mzbench_api/src/mzb_pipeline.erl"},
                            {line,172}]}]
ioolkos commented 6 years ago

Hi @eckucukoglu thanks for checking this out! :)

Can you see my note on https://github.com/erlio/vmq_mzbench/issues/5#issuecomment-278266252 There is a weird correlation there. But it can absolutely be solved by adjusting wait-times.

Let me know if you need more specific help any time.

eckucukoglu commented 6 years ago

Yes, it works. I just created this issue to notify. :) Thank you.