Re: [I] [Bug] In 5.3.3 and 5.3.4, within the master-slave Broker cluster, when the master Broker is down, can not consume the backlog of messages from the standby Broker. [rocketmq]

Fri, 28 Nov 2025 04:10:39 -0800 


zergduan commented on issue #9879:
URL: https://github.com/apache/rocketmq/issues/9879#issuecomment-3589090936

   > 有配置这两个参数吗
   > 
   > <img alt="Image" width="834" height="377" 
src="https://private-user-images.githubusercontent.com/49970811/520047549-9eb9e540-73a9-407c-8461-08da8c243232.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjQzMzE2MjAsIm5iZiI6MTc2NDMzMTMyMCwicGF0aCI6Ii80OTk3MDgxMS81MjAwNDc1NDktOWViOWU1NDAtNzNhOS00MDdjLTg0NjEtMDhkYThjMjQzMjMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTExMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMTI4VDEyMDIwMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNiZjgxYmM2NDdiOWU4ZjM1NmVmNzkxMmFkMWZmODRhMzI0MDY2YWJjZmU4MmMxZGU1YTY0M2FlZDMxNTAyN2YmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.t5iyjKG03JU-6PWyyg7ykvdsaVyO7VAec7twz9pnizE";>
   
   多谢，我已经在NameServer和Broker上启用了这两个参数为true，目前：
   
   1. 当2个Master宕机时，2个Slave已经可以激活，如下图：
   
   <img width="2838" height="318" alt="Image" 
src="https://github.com/user-attachments/assets/36d09db7-6bf3-4532-bed9-04a33ff92ec7";
 />
   
   2. 虽然2个Slave已经激活，但是消费者连接到Slave后，依然无法消费堆积的消息：
   Slave Broker的 Broker.log日志中可以看到：
   消费者已经连接到SLAVE，尝试消费
   
   <img width="2703" height="884" alt="Image" 
src="https://github.com/user-attachments/assets/5871e1aa-54f6-461a-8b4e-8113e01e3b7a";
 />
   
   但是消费者没有收到任何消息：
   
   <img width="1830" height="840" alt="Image" 
src="https://github.com/user-attachments/assets/b52c937f-abc6-43cb-bca3-5988983ffcba";
 />
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to