[Bug] Lite-selective consumer groups are reported as CLUSTERING by the Proxy Admin surface

未关闭
  • 哪里不对？
#11,371 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@iloveeyjafjalla 已经在做这个了。

开始于 2026年10月12日。

  • #11372 来自 @iloveeyjafjalla —— 未关闭

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
java
领域
backend, distributed-systems

调研方向

Start with the message model converter used by ListSubscription, DescribeSubscription, and ListConsumerConnection, then inspect the existing tests for those admin responses. Confirm the returned message_model for a lite consumer group is LITE_SELECTIVE. An open pull request, #11372, is already linked to this issue.

由索引模型根据 Issue 内容生成。

描述

Before Creating the Bug Report
  • I found a bug, not just asking a question, which should be created in GitHub Discussions.
  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
  • 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:

// 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:

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.

主要语言
Java
星标
22.7k
派生
12k
平均合并
3 天 18 小时
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

apache/rocketmq 的其他 Issue

查看 apache/rocketmq 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。