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

Open
  • Is something wrong?
#11,371 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@iloveeyjafjalla is already working on this.

Since Oct 12, 2026.

  • #11372 by @iloveeyjafjalla — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
java
Domain
backend, distributed-systems

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Java
Stars
22.7k
Forks
12k
Avg merge
3d 18h
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/rocketmq

All issues in apache/rocketmq

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.