tju-yxq opened a new issue, #2595: URL: https://github.com/apache/rocketmq-dashboard/issues/2595
## Problem `ClusterService.listClusters()` enriches every discovered cluster independently: ```java discovered.forEach(this::enrichWithLiveConfig); ``` Each `enrichWithLiveConfig` call walks that cluster’s brokers and attempts a live broker-config read until one succeeds. This is correct for distinct clusters, but discovery can return multiple registry views that contain the same broker. In that case the same broker address is retried once per cluster. If that broker is unavailable, each duplicate repeats the same failing admin call before falling back to persisted configuration. The selected-instance path has the same behavior. ## Expected behavior - Keep attempting distinct broker addresses in discovery order. - Record broker addresses already attempted while enriching one discovery result. - Do not repeat a live broker-config read for the same broker address in the same discovery call. - Preserve the persisted-config fallback for every cluster whose brokers are unavailable or already attempted. - Keep single-cluster detail behavior unchanged. ## Verification scope Tests should prove that duplicate clusters referencing the same broker make exactly one live-config read for that broker and each duplicate receives its own persisted fallback configuration. -- 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]
