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
Doing MQTT benchmark ocasionally triggers that Zilla sends corrupt data to Kafka.
[KafkaApi-1] Closing connection due to error during produce request with correlation id 171 from client id zilla with ack=0
kafka | Topic and partition to exceptions: mqtt-messages-0 -> org.apache.kafka.common.errors.CorruptRecordException (kafka.server.KafkaApis)
To Reproduce
Steps to reproduce the behavior:
Run Zilla locally with basic mqtt-kafka config and local Kafka
Notice that the MQTT client gets disconnected with reason code 131 (Implementation specific error)
This disconnect is sent due to a corrupt record being published to Kafka, and Kafka resets the connections
In the Kafka logs you can observe the issue:
[KafkaApi-1] Closing connection due to error during produce request with correlation id 171 from client id zilla with ack=0
kafka | Topic and partition to exceptions: mqtt-messages-0 -> org.apache.kafka.common.errors.CorruptRecordException (kafka.server.KafkaApis)
Describe the bug
Doing MQTT benchmark ocasionally triggers that Zilla sends corrupt data to Kafka.
To Reproduce
Steps to reproduce the behavior:
./emqtt_bench pub -h localhost -p 1883 -q 0 -c 100 -I 100 -L 50000 -t bench/%i
kafka_corrupt.zip
The text was updated successfully, but these errors were encountered: