yyqdbngt opened a new pull request, #2873: URL: https://github.com/apache/rocketmq-dashboard/pull/2873
## Summary - Cap `RocketMQClientProvider.findConsumerConnections` at 200 consumer-group connection queries per scan (`MAX_CONSUMER_GROUPS_SCANNED`) - Log a warning when the cap is hit so partial listings are visible in the server log - Add a regression test with a 300-group cluster asserting exactly the cap is queried ## Why The consumer connection page scans every subscription group in the cluster and issues one sequential `examineConsumerConnectionInfo` admin RPC per group, with no cap. On a long-running cluster whose group table has grown to thousands of entries, a single page load issues thousands of sequential broker round-trips and can hold the request thread for minutes — far past the frontend's request timeout. The cap bounds the worst case at the cost of a logged partial listing (system groups still don't count against it). ## Testing - `mvn -Dtest='RocketMQClientProviderTest,ProducerConnectionServiceTest,ClientServiceTest' test` → RocketMQClientProviderTest 25/25 (incl. new cap regression), ProducerConnectionServiceTest 7/7, ClientServiceTest 5/5 -- 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]
