Consumer progress rows interleave topics with equal queue IDs
Maintainers usually reply within 3 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Find the Apache provider's getGroupProgress implementation in the rocketmq-dashboard source and inspect how its consumer-group queue progress rows are sorted. Reproduce the order with the linked offset map described in the issue, then verify that rows remain grouped by broker and are sorted by topic and queue ID with deterministic case-sensitive tie-breakers.
Written by the indexing model from the issue text.
Description
Problem
The Apache provider sorts consumer-group queue progress by broker and queue ID only. Different topics commonly have the same queue IDs on the same broker, so their rows compare equal and retain the order of the broker's offset map. The consumer-group detail table can therefore interleave topics or change row order between responses even when offsets are unchanged.
Reproduction
Return offset rows for TopicB/queue 0, TopicA/queue 1, and TopicA/queue 0 on the same broker. getGroupProgress currently returns topics in TopicB, TopicA, TopicA order. A regression using a linked offset map demonstrates this on the current rocketmq-studio source.
Expected
Keep broker grouping, then sort by topic and queue ID with deterministic case-sensitive tie-breakers. This makes queue progress stable and keeps a topic's queues together.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 709
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 166
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/rocketmq-dashboard
-
[Doc] Align documented Maven image with deployment defaultPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
apache/rocketmq-dashboard#7248 ·
Maintainers usually reply within 3 days
-
[rmqctl][Bug] Windows build script fails when the output directory is absentPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/rocketmq-dashboard#7243 ·
Maintainers usually reply within 3 days
-
[Bug] Large consumer queue inventories crash health diagnosticsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/rocketmq-dashboard#7242 ·
Maintainers usually reply within 3 days
-
[Bug] Traffic insights classify rounded values at health thresholdsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/rocketmq-dashboard#7240 ·
Maintainers usually reply within 3 days
-
[Bug] rmq.acl.create/update report a different creation time than rmq.acl.get for the same rulePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
apache/rocketmq-dashboard#7238 ·
Maintainers usually reply within 3 days
All issues in apache/rocketmq-dashboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
account bug communication lecture
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area/server bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/java-sdk#1196 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ignatov/intellij-erlang#1093 ·