Aias00 opened a new issue, #1057: URL: https://github.com/apache/rocketmq-dashboard/issues/1057
## Problem Runtime operations currently use a singleton `DefaultMQAdminExt` configured from one global NameServer address. Instance-scoped pages can therefore display or mutate the default cluster even when another instance is selected. ## Scope - Resolve a selected `instanceId` to the persisted instance endpoint. - Reuse the existing `MqAdminExtFactory` cache to obtain an AdminClient for that endpoint. - Establish the resolver as the shared runtime-operation foundation. - Use DLQ list and resend as the first consumer, including API and UI context propagation. ## Follow-up Client connections, message query, and trace will migrate in separate focused PRs under #982. ## Track Track 1 / Control Plane multi-instance runtime 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]
