[Bug] when orderly consumer consume message fails time reach the maxReconsumeTimes, the %RETRY% topic will create in broker that has not contain the orignial topic
- Dominant language
- Java
- Stars
- 22.6k
- Forks
- 12k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 26
Description
### Before Creating the Bug Report
- [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions).
- [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate.
- [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
### Runtime platform environment
linux
### RocketMQ version
RocketMQ 5.3.3
proxy cluster mode
### JDK Version
1.8
### Describe the Bug
use proxy cluster mode and 5 master broker(A B C D E), create topic t in A B C , and create orderly consumer connect proxy to consume message and set maxReconsumeTimes, when consume fails time reach the maxReconsumeTimes, the %RETRY%consumergroup will create in A B C D E broker, i wish the %RETRY% only create in A B C 。
i read the code, orderly consumer mode the %RETRY% topic create depend on TBW102 system topic
### Steps to Reproduce
use proxy cluster mode and 5 master broker(A B C D E), create topic t in A B C , and create orderly consumer connect proxy to consume message and set maxReconsumeTimes, when consume fails time reach the maxReconsumeTimes, the %RETRY%consumer group will create in A B C D E broker, i wish the %RETRY% only create in A B C
### What Did You Expect to See?
i wish the %RETRY% only create in A B C 。
### What Did You See Instead?
the %RETRY%consumergroup will create in A B C D E broker
### Additional Context
_No response_
Contributor guide
Research direction
Start by reproducing the proxy cluster setup with five master brokers, a topic on only A, B, and C, and an orderly consumer reaching maxReconsumeTimes. Trace retry-topic creation through the TBW102 system topic handling; done means the %RETRY% topic is created only on the brokers that contain the original topic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100