[Bug] RMQ 5.3.3版本消费端consumer接收不到消息
- 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
CenterOS7
### RocketMQ version
RocketMQ 版本经测试 5.3.3 版本以及 5.3.2 版本发现此问题,5.2.0 版本无此问题!
### JDK Version
1.8
### Describe the Bug
Consumer 所在的服务器有 2 个ip,一个是10.10.20.151,一个是192.168.20.151。SpringBoot 服务配置的 server.address 是10.10.20.151。生产服务生产消息后,消费端接收不到数据。通过 RMQ 的控制台 的 Consumer 页面,找到对应的 topic ,点击右侧的 consume detail,发现consumerClient的ip为192.168.20.151。生产者、RMQ 服务的 ip 都使用的 10 网段 ip。未升级 RMQ 前的版本是 5.2.0,升级到5.3.3版本后发现前面提到的问题,经测试 5.3.2 版本也有该问题。目前项目已经退回 5.2.0 版本。同时发现 5.3.3 版本在使用 dashboard 查看消息时,message 页面的详情中的 Consumer 会出现两个,其中一个不知道是哪来的,项目中从未定义过。比如项目中定义的 Topic 为 test-app-consumer-MQ_TEST_INFO,结果消息详情的 consumerGroup中出现了test-MQ_TEST_INFO的消费组,而在 dashboard 的 consumer 页面找不到此消费组,通过rocketmqadmin通过命令也查不到。
### Steps to Reproduce
见上面的描述
### What Did You Expect to See?
消费端能够正常消费到消息
### What Did You See Instead?
消费端未能收到消息
### Additional Context
_No response_
Contributor guide
Research direction
Start with the reported SpringBoot server.address setting and compare consumer behavior between RocketMQ 5.2.0 and 5.3.2/5.3.3. Inspect the Dashboard Consumer page and consume detail, then use rocketmqadmin to investigate the unexpected consumer group. Done means the consumer advertises the 10.10.20.151 address and receives messages normally on the newer versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100