apache / apache/rocketmq-externals
[rocketmq-iot-bridge]MQTT broker quality level qos1 (at least one) between the publisher client and mqtt broker
- Dominant language
- Java
- Stars
- 4.6k
- Forks
- 3k
- Avg merge
- 2h 33m
- Merged PRs (30d)
- 1
Description
- The iot-bridge broker is implemented based on rocketmq, it is necessary to ensure the qos1 between the publisher client and rocektmq, between rocektmq and subscriber client.
- This issue is resolved the publisher client and mqtt broker.
1. Please describe the issue you observed:
- MQTT broker receive publisher client's message and send it to rocketMQ, it will not send the suback protocol message to the publisher until it succeeds.
- When MQTT broker send rocketMQ messages failed, Broker will periodically retry sending failed messages, can't more than the maximum retry of times (configurable)
- qos1 has the possibility of message duplication.

2. Please tell us about your environment:
Linux
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the rocketmq-iot-bridge MQTT broker implementation and trace the publisher message path into RocketMQ. Check how SUBACK is sent, how failed sends are retried and bounded, and how QoS 1 duplication is handled. Done means the publisher-to-broker path meets the described QoS 1 behavior, with tests covering success and failed-send cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100