You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2021/11/25 05:52:48 UTC

[GitHub] [rocketmq-externals] bobosmile1170556238 opened a new issue #852: When a primary node [broker-b] of a broker goes down, the broker [broker-b] not exist will be reported when querying the message

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: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org