RockteMQ-AI commented on issue #2151: URL: https://github.com/apache/rocketmq-dashboard/issues/2151#issuecomment-5283882599
**Issue Evaluation** Category: `bug` | Status: **Confirmed** When switching instances, the new cluster request starts but the previous instance topology rows remain visible. If the new request fails, operators see stale data from the wrong instance context indefinitely. **Root Cause:** Missing cleanup of previous topology state when instance scope changes; no error-state reset. **Impact:** Operators may read or act on data from the wrong RocketMQ instance — a significant operational risk. **Severity:** medium-high — stale topology can lead to incorrect operational decisions. Suggested fix: clear all topology rows immediately when the instance selector changes. On request failure, show an empty state rather than restoring previous data. --- *Automated evaluation by github-manager-bot* -- 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]
