You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When performance testing QoS2 publish, after a while Zilla get's stuck on allowing MQTT clients to connect. We start the group stream from MQTT-Kafka, the KafkaClientGroupFactory sends the FindCoordinatorRequest, Kafka replies with the FindCoordinatorResponse, but we never decode that packet.
To Reproduce
Steps to reproduce the behavior:
Run Zilla locally with basic mqtt-kafka broker config
Run emqtt bench pub until the the benchmark hangs (you might need to stop and run multiple times): ./emqtt_bench pub -h localhost -p 1883 -q 2 -c 100 -I 10 -t bench/%i
After that not even a simple connection is accepted by Zilla. Try: mosquitto_pub --url mqtt://localhost:1883/qos2 -V 5 -q 2 --message "QOS 2" -d -i "client-id"
The client hangs until timeout
To further debug, put a breakpoint on these codes: KafkaClientGroupFactory.ClusterClient#doEncodeFindCoordinatorRequest KafkaClientGroupFactory#decodeFindCoordinatorResponse
Notice that decodeFindCoordinatorResponse is never called.
I've ran local Kafka (bitnami/kafka:3.5), after a zilla restart the issue is resolved.
The text was updated successfully, but these errors were encountered:
Describe the bug
When performance testing QoS2 publish, after a while Zilla get's stuck on allowing MQTT clients to connect. We start the group stream from MQTT-Kafka, the KafkaClientGroupFactory sends the FindCoordinatorRequest, Kafka replies with the FindCoordinatorResponse, but we never decode that packet.
To Reproduce
Steps to reproduce the behavior:
./emqtt_bench pub -h localhost -p 1883 -q 2 -c 100 -I 10 -t bench/%i
mosquitto_pub --url mqtt://localhost:1883/qos2 -V 5 -q 2 --message "QOS 2" -d -i "client-id"
To further debug, put a breakpoint on these codes:
KafkaClientGroupFactory.ClusterClient#doEncodeFindCoordinatorRequest
KafkaClientGroupFactory#decodeFindCoordinatorResponse
Notice that decodeFindCoordinatorResponse is never called.
I've ran local Kafka (bitnami/kafka:3.5), after a zilla restart the issue is resolved.
The text was updated successfully, but these errors were encountered: