RockteMQ-AI commented on issue #4612: URL: https://github.com/apache/rocketmq-dashboard/issues/4612#issuecomment-5751645142
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The bug is confirmed. `loadRegistryClusters` and `loadNsRegistry` catch failed API calls by setting empty arrays without setting any error state. Since these loaders run only once on mount (not in the 2s auto-refresh cycle), a transient 5xx permanently empties the Broker/Proxy/NameServer registry tables while the green live-refresh indicator continues to signal health. **Root Cause:** Error handling in `web/src/pages/cluster/index.tsx:215-218, 235-237, 252-254` resets data to empty instead of surfacing an error state. The live indicator is decoupled from registry load health. **Impact:** Operators see empty cluster inventories with a green health indicator during transient failures — misleading "no clusters" + "connection healthy" simultaneously. **Severity:** Medium — transient trigger but confusing UX; no data mutation risk. The existing `instanceLoadError` pattern in the same file demonstrates the correct approach (error state + retry panel). The registry loaders should follow the same pattern. --- *Automated evaluation by RocketMQ AI Assistant* -- 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]
