You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/08/12 08:11:54 UTC
[I] [Studio][Bug] Preserve identical producer connections across RocketMQ clusters [rocketmq-dashboard]
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][Bug] Preserve identical producer connections across RocketMQ clusters [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #1991:
URL: https://github.com/apache/rocketmq-dashboard/issues/1991#issuecomment-5264171300
**Issue Evaluation**
Category: `bug` | Status: **Needs Verification**
Thank you for reporting this issue. To proceed with verification, please provide:
- Version/tag where this occurs
- Steps to reproduce
- Expected vs actual behavior
- Relevant logs or stack traces
---
*Automated evaluation by RocketMQ AI Assistant*
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][Bug] Preserve identical producer connections across RocketMQ clusters [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #1991: [Studio][Bug] Preserve identical producer connections across RocketMQ clusters
URL: https://github.com/apache/rocketmq-dashboard/issues/1991
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][Bug] Preserve identical producer connections across RocketMQ clusters [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #1991:
URL: https://github.com/apache/rocketmq-dashboard/issues/1991#issuecomment-5349553080
This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org