unbridled-41 opened a new issue, #5967: URL: https://github.com/apache/rocketmq-dashboard/issues/5967
### Studio Version branch: `rocketmq-studio` @ `7e7aa344` ### Runtime Environment Backend tests: `cd server && mvn -o -B -ntp test -Dtest='ProxyConsumerResolverTest'`. ### Connected RocketMQ Cluster A gRPC (proxy) cluster with more than one proxy and a group whose clients are spread across them. ### Describe the Bug `ProxyConsumerResolver.resolveConsumerConnectionStatus` returns as soon as one proxy answers with a connection. Each proxy knows only the clients connected to it, so the group's connection set, subscription table and channel list were reported from a single proxy as the whole group. Consumers: the group list (`instances`, `onlineInstances`), the group detail read and the AI group-detail verdict. The sibling client scan in the same package already unions every proxy (`RocketMQClientProvider.findConsumerConnections`). ### Steps to Reproduce 1. Connect two clients of one group to different proxies. 2. Open the consumer-group page (or the AI group detail): only one proxy's client appears. ### What Did You Expect to See? The union of what the proxies report. ### What Did You See Instead? The first answering proxy's subset, presented as the group. ### Impact A gRPC group's online clients, subscribed topics and instance rows are under-reported with a plausible-looking number, and the AI health verdict reasons on that subset. ### Acceptance Criteria The resolver merges every proxy's answer (connections deduped, subscription tables unioned), keeps the offline-vs-unavailable distinction, and a regression test pins the union. **Corresponding PR:** #ISSUEPR# -- 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]
