yuluo-yx opened a new issue, #2899: URL: https://github.com/apache/rocketmq-dashboard/issues/2899
### Problem\nAfter topology loads for one instance, switching to another instance whose cluster request fails leaves the first instance's brokers, NameServers, and proxies on screen. The export action also remains enabled, so stale topology can be exported while the second instance is selected.\n\n### Reproduction\n1. Load Broker Cluster with instance A and a successful topology response.\n2. Switch the instance selector to instance B.\n3. Make the instance B cluster request fail.\n4. Observe that instance A's broker rows remain visible.\n\n### Expected behavior\nA failed current-instance request clears the previous topology and disables export. Stale or superseded requests must still be ignored.\n\n### Proposed fix\nClear all topology datasets only when the active request fails, with a regression test covering success → instance switch → failure. -- 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]
