[Bug] RMQ5.3.3 PROXY部署模式,运维工具无法正常查询消费者链接情况
- Dominant language
- Java
- Stars
- 22.6k
- Forks
- 12k
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 27
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
OS: MACOS 14.5
### RocketMQ version
RMQ: 5.3.3
### JDK Version
JDK: 1.8.0
### Describe the Bug
我用的部署模式是集群PROXY,GRPC链接方式。 正常情况下生产和消费都可以正常使用,但是运维工具和rocketmq-dashboard都无法有效的监测消费者的情况。consumerConnection命令提示No topic route info in name server for the topic: %RETRY%case-sys-test, 手动创建了这个队列之后,就会提示 not online BROKER: 172.31.140.89:10911。
### Steps to Reproduce
1. 创建topic
2. 生产者消费者正常生产和消费
3. 运维工具使用命令consumerConnection即报错,rocketmq-dashboard也无法查看消费者情况
### What Did You Expect to See?
想要知道如何解决这个问题,proxy部署模式下如何检测消费者情况
### What Did You See Instead?
无法正常查询消费者情况,运维命令报错
### Additional Context
nothing
Contributor guide
Research direction
The payload names no source files, tests, or entry points. Reproduce the three listed steps with RocketMQ 5.3.3 in clustered PROXY mode using gRPC, then trace the consumerConnection command and dashboard query path. Done means consumer connections can be queried and displayed without the missing route or offline broker errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- backend, observability, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100