RockteMQ-AI commented on issue #4506: URL: https://github.com/apache/rocketmq-dashboard/issues/4506#issuecomment-5712547763
**Issue Evaluation** Category: `bug` | Status: **Confirmed** Verified against current `master` (987b748e). The analysis is accurate: - `PlatformClusterResolver.collect()` iterates over `manageableInstances()` and stores results in a `LinkedHashMap` using `putIfAbsent(clusterName, cluster)`. When two managed instances expose a cluster with the same name (e.g. `DefaultCluster`), the second instance's clusters are silently dropped. - `require(clusterName)` and `resolveInstanceId(clusterName)` resolve against this deduplicated map, so they deterministically return the first instance's cluster — even when the operator intended a different one. - Since current tools are read-only, this is a diagnostic correctness issue rather than a wrong-cluster mutation risk. The proposed fail-closed design (409 on ambiguous names, preserving per-instance results for `require()` while keeping `scan()` deduplicated) is sound and backward-compatible for the common case of unique cluster names. **Severity:** Medium — affects multi-instance Studio deployments with overlapping cluster names. **Impact:** AI/MCP tool diagnostics may report configuration from the wrong instance. An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager* -- 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]
