Aias00 opened a new issue, #1991: URL: https://github.com/apache/rocketmq-dashboard/issues/1991
## Problem The Track 1 client connections view can aggregate Producer connections across every RocketMQ cluster in an Apache instance. `RocketMQClientProvider` now discovers and returns each connection's actual `clusterName`, but the Producer deduplication key still contains only `producerGroup`, `clientId`, and `remoteIP`. If two clusters legitimately contain an identical Producer identity, the second row is dropped by `putIfAbsent`. The UI then reports only one cluster even though both clusters have an online Producer. ## Reproduction 1. Configure one Apache instance whose NameServer topology exposes `cluster-a` and `cluster-b`. 2. Register a Producer with the same group, client ID, and remote address in both clusters. 3. Call `GET /api/clients?instanceId=<id>&type=Producer` without a `clusterId` filter. 4. Only one connection is returned because the deduplication key does not include the discovered cluster. ## Expected behavior - Duplicate Broker reports inside the same cluster are still collapsed. - Identical Producer identities in different clusters remain separate rows. - Each row retains its discovered `clusterName`. ## Scope Update the Producer aggregation key in `RocketMQClientProvider` and add a focused regression test. No API contract or persistence change is required. Track 1: unified control plane client management. -- 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]
