Aias00 opened a new issue, #1660: URL: https://github.com/apache/rocketmq-dashboard/issues/1660
## Problem `RocketMQDashboardProvider.collectDashboardData()` calls `examineTopicRouteInfo(topic)` once for every non-system Topic solely to derive per-cluster topic counts. Large clusters turn one overview refresh into hundreds or thousands of sequential NameServer route requests. ## Why this needs a design decision A Topic can span brokers and cluster ownership is not represented in the topic list. Skipping route lookup without a replacement would make per-cluster counts incorrect. ## Proposed direction - Evaluate a bounded/cached route-resolution strategy with an explicit freshness policy, or a backend aggregate endpoint. - Make any partial result visible to the UI rather than reporting it as a complete count. - Add a large-topic-count benchmark and ensure refresh latency/RPC volume remain bounded. ## Track Track 1 / dashboard runtime observability. -- 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]
