bobosmile1170556238 opened a new issue #852:
URL: https://github.com/apache/rocketmq-externals/issues/852


   I think this is a a rocketmq-console bug.
   When a primary node [sync-async-broker-b] of a broker goes down, the broker 
[sync-async-broker-b] not exist will be reported when querying the message.
   
   Can I change to the primary node and get data from the slave node when it 
goes down?
   
   version: rocketmq4.8.0


-- 
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