Aias00 opened a new issue, #1126:
URL: https://github.com/apache/rocketmq-dashboard/issues/1126
## Problem
The Topic detail modal requests `/api/topics/{name}/routes` and
`/api/topics/{name}/consumers` without an `instanceId`. The controller and
`MetadataService` consequently use the process-wide metadata provider rather
than the endpoint of the selected Studio instance.
In a multi-instance deployment, route and consumer information can therefore
be read from a different RocketMQ cluster than the Topic selected in the UI.
## Expected behavior
- The web client passes the selected `instanceId` to both diagnostic
endpoints.
- The server resolves the corresponding instance endpoint through the
runtime admin-client path introduced by #1058.
- Missing or unknown instances return the existing structured error
semantics instead of falling back to the global client.
- Existing mock-mode behavior remains unchanged.
## Scope
This issue covers only read-only Topic route and consumer diagnostics. Topic
mutations and consumer-group diagnostics remain separate follow-ups.
--
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]
