When a primary node [broker-b] of a broker goes down, the broker [broker-b] not exist will be reported when querying the message

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

Start by reproducing the rocketmq-console message query with the primary node of sync-async-broker-b unavailable on RocketMQ 4.8.0. Investigate how the console resolves the broker and whether the slave can serve the query. Done means the expected behavior is documented or the query no longer reports the broker as nonexistent when the primary is down.

Written by the indexing model from the issue text.