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]

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