X-LightYear opened a new issue, #4992:
URL: https://github.com/apache/rocketmq-dashboard/issues/4992

   ## Problem
   
   The Studio cluster list endpoint accepts an `instanceId`, and the frontend 
passes the selected instance when loading cluster diagnostics. On the Apache 
provider path, however, the instance-scoped `ClusterProvider` overload is not 
implemented by `RealClusterProvider`.
   
   ## Reproduction
   
   1. Configure an Apache RocketMQ instance with a reachable cluster.
   2. Open the Studio Broker Cluster page or call `GET 
/api/clusters?instanceId=<instance-id>`.
   
   ## Expected behavior
   
   The selected instance's discovered clusters are returned.
   
   ## Actual behavior
   
   The response is an empty list even though the selected instance has a 
reachable cluster. The default `ClusterProvider.discoverClusters(String)` 
implementation returns an empty list for a non-blank instance ID.
   
   ## Root cause
   
   `RealClusterProvider` implements only the unscoped `discoverClusters()` 
method. The instance-scoped call therefore uses the SPI default instead of 
resolving the selected instance's runtime admin client.
   
   ## Scope
   
   Implement the instance-scoped discovery path in `RealClusterProvider` while 
preserving the existing unscoped behavior.
   
   ## Regression evidence
   
   
`RealClusterProviderTest.discoverClustersForSelectedInstanceShouldReturnItsClusters`
 fails on the current implementation with an empty result and passes after the 
instance-scoped provider path is implemented.
   


-- 
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]

Reply via email to