Open muzhi9018 opened 4 months ago
Could you also print message id in your consumer?
Could you also print message id in your consumer?
The one on the left is the producer console, which prints the message id; the one on the right is the consumer console, which prints the message key.
Try using the latest version to see if it can be reproduced
Before Creating the Bug Report
[x] I found a bug, not just asking a question, which should be created in GitHub Discussions.
[X] I have searched the GitHub Issues and GitHub 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
宿主机 Win 11 23H2 Docker 容器基础镜像 ubuntu:22.04
RocketMQ version
Rocket MQ 版本 5.1.4 Rocket MQ 客户端版本 5.0.6 (rocketmq-client-java) 客户端 Maven 坐标
JDK Version
Zulu JRE 17.0.11
Describe the Bug
使用 Docker Compose 部署 2 个 Master Broker; 2 个 Slave Broker; 当其中一个 Master Broker 宕机之后会有部分消息一直重复消费
Steps to Reproduce
Dockerfile 如下
docker-compose.yaml 如下
Master Borker a 配置文件如下 broker-master-a.conf
Slave Borker a01 配置文件如下 broker-slave-a01.conf
Master Borker b 配置文件如下 broker-master-b.conf
Slave Borker b01 配置文件如下 broker-slave-b01.conf
代理组件配置文件如下 rmq-proxy.json
正常启动 消息生产者,和消息消费者 消息生产者代码如下
消息消费者代码如下
连续发送多条消息 中途关闭 broker-master-a 已经发送的部分消息一直重复消费 消费者控制台可以清除的看到 消息被重复消费
dashboard
后续 broker-master-a 启动,则回复正常
What Did You Expect to See?
配置文件 slaveReadEnable 设置为 false 希望 Master 宕机之后能正常 消费者不要重复一直消费
What Did You See Instead?
部分消息一直重复消费
Additional Context
No response