014-code opened a new pull request, #10480: URL: https://github.com/apache/rocketmq/pull/10480
### Which Issue(s) This PR Fixes Fixes #9796 ### Brief Description This PR supports `GET_CONSUMER_RUNNING_INFO` in proxy cluster mode. Previously, `mqadmin consumerStatus` against the proxy cluster remoting port failed with: `request type 307 not supported` ### Root Cause The proxy remoting server did not register `RequestCode.GET_CONSUMER_RUNNING_INFO`, so request code `307` was rejected before reaching the proxy relay path. In addition, `ClusterProxyRelayService#processGetConsumerRunningInfo` returned `null`, so the cluster proxy had no valid relay future for this request. ### How Was This Fixed? - Register `RequestCode.GET_CONSUMER_RUNNING_INFO` in `RemotingProtocolServer`. - Add request handling in `ConsumerManagerActivity`. - Locate the target consumer channel by `consumerGroup` and `clientId`. - Relay the request through the proxy-managed `ProxyChannel`. - Encode and write `ConsumerRunningInfo` back to the original admin request. - Make `ClusterProxyRelayService#processGetConsumerRunningInfo` return a `CompletableFuture` instead of `null`. ### Tests Added test file: `proxy/src/test/java/org/apache/rocketmq/proxy/remoting/activity/ConsumerManagerActivityTest.java` Verified the following test methods passed in IDEA: - `testGetConsumerRunningInfo` - `testGetConsumerRunningInfoWhenConsumerNotOnline` -- 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]
