Aias00 opened a new issue, #1527: URL: https://github.com/apache/rocketmq-dashboard/issues/1527
## Problem Cluster configuration updates accept `instanceId` and route the live Broker update through the selected instance. However, the fallback snapshot is persisted in `ClusterRepository` under only `clusterId`. When two managed instances expose the same logical cluster ID, a later unavailable/live-read fallback can return one instance's configuration to the other. ## Scope - Key persisted fallback Cluster configuration by both `instanceId` and `clusterId`. - Preserve the existing unscoped behavior for legacy calls without an instance. - Add service coverage proving same-named clusters from different instances do not share fallback config. ## Track Track 1 / ARCH-01 multi-instance Cluster 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]
