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

オープン
  • 何か問題がありますか？
#11,371 コメント 1 件 リアクション 0 件 担当者 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時間
マージ済み PR（30日）
17

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

apache/rocketmq のほかの issue

apache/rocketmq の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。