Aias00 opened a new issue, #1243: URL: https://github.com/apache/rocketmq-dashboard/issues/1243
## Problem Broker configuration reads and writes instantiate the AdminClient from the global `studio.rocketmq.namesrv-addr`. In a multi-instance Studio deployment, the Cluster page can therefore read or update the wrong RocketMQ cluster. ## Expected behavior Cluster configuration API contracts carry the selected Apache `instanceId`; Broker config reads and writes use the existing runtime AdminClient resolution path. Missing, unknown, and non-Apache instances return structured errors rather than falling back to the global endpoint. ## Scope Track 1 multi-instance control-plane correctness. This issue covers Broker configuration only; broader cluster discovery/action routing stays separate. ## Evidence - `server/src/main/java/org/apache/rocketmq/studio/provider/apache/RocketMQBrokerConfigService.java:43` - `server/src/main/java/org/apache/rocketmq/studio/cluster/broker/ClusterService.java:78` -- 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]
