Aias00 opened a new issue, #1659: URL: https://github.com/apache/rocketmq-dashboard/issues/1659
## Problem `RocketMQMetadataProvider.getTopicConsumers()` first calls `queryTopicConsumeByWho(topic)`, then performs up to two Admin RPCs per returned group: `examineConsumeStats(group, topic)` and `examineConsumerConnectionInfo(group)`. A Topic with many subscribers therefore produces unbounded sequential RPC latency and can overload the selected NameServer/Broker. ## Why this needs an API design The current endpoint returns a complete, live consumer list. Adding a hidden cap would silently omit consumer groups, which is unsafe for a control plane. ## Proposed direction - Add explicit pagination or a summary/detail split to the Topic consumer API. - Return a visible completeness indicator and total group count. - Fetch expensive lag/connection diagnostics only for the requested page or explicit detail view. - Add bounded-RPC and partial-result regression tests. ## Track Track 1 / runtime diagnostics performance. -- 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]
