Aias00 opened a new issue, #1697: URL: https://github.com/apache/rocketmq-dashboard/issues/1697
## Bug `GET /api/clients?instanceId=<id>` returns connections whose `clusterName` is `null`. `RocketMQClientProvider` passes the optional request filter directly into every result instead of deriving the Broker-to-Cluster mapping from `ClusterInfo`. Consequently, the Client Connections page cannot build its cluster filter from real data. The optional `clusterId` parameter is also not applied to the Broker scan: requesting a single cluster still reads all Broker producer tables and subscription groups. ## Expected behavior - Every returned Apache Remoting client connection carries its discovered RocketMQ cluster name. - When `clusterId` is supplied, scans are limited to that cluster's master Brokers. - Unknown cluster filters return an empty result without querying unrelated Brokers. ## Scope Update `RocketMQClientProvider` and its unit tests only. The change uses the existing `ClusterInfo.clusterAddrTable` and `brokerAddrTable` topology response; it adds no API or persistence dependency. -- 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]
