Loyal-Young opened a new issue, #7250: URL: https://github.com/apache/rocketmq-dashboard/issues/7250
## 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
