lizhimins opened a new pull request, #2342: URL: https://github.com/apache/rocketmq-dashboard/pull/2342
## Summary - Add a nameserver registry (`rmq_nameserver`) with CRUD endpoints (`/api/nameservers`, `/api/nameservers/registry/*`) storing cluster access entries (nameserver address, k8s namespace, k8s ID). - Drive cluster discovery from the registry: probe every registered nameserver address concurrently (`examineBrokerClusterInfo`, the RPC behind `mqadmin clusterList`), 15s timeout per entry, unreachable entries skipped with a warning. - Discover online proxies indirectly through the heartbeat-syncer consumer group (`CID_DefaultHeartBeatSyncerTopic`) connections — open-source proxies never register with the nameserver, but every proxy node consumes this broadcast group. - Resolve Remoting client version codes via `MQVersion.getVersionDesc` (e.g. 513 -> V5_5_0). - Auto-create missing `%RETRY%<group>` topics before group diagnostics (POP groups only get them lazily) and degrade "group not online" (CODE 206) to an empty result instead of a 502. - Broker / Proxy / Clients pages now read from the registry-driven `GET /api/clusters/registry`; the Clients page selects a NameServer first, then a broker cluster under it. ## Test plan - [x] Backend full suite (1224 tests) - [x] Frontend full suite (93 files) - [x] Live verification: registry probe returns online clusters/proxies; group subscriptions/progress degrade gracefully -- 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]
