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

Aperta
  • Qualcosa non va?
#11,371 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@iloveeyjafjalla ci sta già lavorando.

Dal 12/10/2026.

  • #11372 di @iloveeyjafjalla — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
java
Ambito
backend, distributed-systems

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Java
Stelle
22.7k
Fork
12k
Merge medio
3g 18h
PR unite (30g)
17

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/rocketmq

Tutte le issue di apache/rocketmq

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.