yuluo-yx opened a new issue, #2151: URL: https://github.com/apache/rocketmq-dashboard/issues/2151
## Affected branch rocketmq-studio at 737a7b4d ## Problem After instance A has loaded, selecting instance B starts a new cluster request but leaves A Broker, NameServer, and Proxy rows visible. If the B request fails, the old A topology remains indefinitely while the selector shows B. Operators can therefore read or act on data from the wrong instance context. ## Expected behavior Changing instance scope should clear all topology immediately, and an active request failure should leave an empty current scope rather than restore or retain previous-instance data. ## Reproduction Load BrokerCluster for instance A, select instance B, and keep the B request pending or reject it. -- 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]
