iloveeyjafjalla opened a new issue, #11371: URL: https://github.com/apache/rocketmq/issues/11371
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment OS: any (proxy module, admin gRPC surface; needs a consumer group of lite consumers) ### RocketMQ version branch: develop Git commit id: 9ea2ccdc2b41445aee5e177e14e501d606f5a1ed (2026-10-08) ### JDK Version Compiler: Temurin 1.8.0_504 (target 1.8, same as CI) ### Describe the Bug Groups of lite consumers are reported as `CLUSTERING` by the admin surface, although the proto has a dedicated consumption model for them. The proxy produces `MessageModel.LITE_SELECTIVE` for lite consumers (`ClientActivity#buildMessageModel` returns it for `LITE_PUSH_CONSUMER` / `LITE_SIMPLE_CONSUMER`), and the admin proto defines the matching value: ```proto // Consumers of the group selectively subscribe to individual lite topics // that are multiplexed onto a shared physical topic. LITE_SELECTIVE = 3; ``` but the converter drops it: ```java switch (messageModel) { case BROADCASTING: return apache.rocketmq.v2.MessageModel.BROADCASTING; case CLUSTERING: default: return apache.rocketmq.v2.MessageModel.CLUSTERING; } ``` `LITE_SELECTIVE` therefore falls into `default` and every `ListSubscription` / `DescribeSubscription` / `ListConsumerConnection` answer reports a lite-selective group as an ordinary clustering group, so a console cannot tell the two apart — even though the model is known and expressible. ### Steps to Reproduce 1. Run a proxy with `grpcAdminServerEnable=true` and a group whose consumers are lite consumers (`ClientType.LITE_PUSH_CONSUMER` / `LITE_SIMPLE_CONSUMER`). 2. Call `ListSubscription{group}` (or `DescribeSubscription` / `ListConsumerConnection`). 3. The returned `subscription_info[].message_model` is `CLUSTERING`. ### Expected behavior `message_model` is `LITE_SELECTIVE` for such a group. ### Actual behavior `CLUSTERING`. ### Additional context Note this is a different path from the wildcard-lite consumption-model work: the converter change only affects groups the proxy already classifies as `LITE_SELECTIVE`, and leaves `BROADCASTING` / `CLUSTERING` / unknown values untouched. -- 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]
