RockteMQ-AI commented on issue #2899: URL: https://github.com/apache/rocketmq-dashboard/issues/2899#issuecomment-5496844193
**Issue Evaluation** Category: `bug` | Status: **Needs Clarification** The dashboard has broker/cluster views in both `frontend-new/src/pages/Cluster/cluster.jsx` and a newer `web/dist/` frontend (BrokerCluster page). However, I could not fully verify the described behavior because: 1. The `frontend-new` cluster page switches clusters via `switchCluster()` which reads from cached `allBrokersData`, but does not have the "instance switching" pattern described (with `selectInstance` / `fetchTopology` / `catch` leaving stale data). 2. The newer `web/` frontend has a `BrokerCluster` component and `clusterService` with mock data, but its source code is not in this repository — only compiled `dist/` assets are present. The described pattern (failed fetch leaving stale topology on screen) is a common React state management issue and is plausible. However, I cannot point to the specific code that exhibits it. Could you clarify: - Which specific file/component in this repository has the described behavior? - Is this about the newer `web/` frontend whose source lives in a separate location? --- *Automated evaluation by RockteMQ-AI* -- 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]
