youngkermit8-coder opened a new issue, #1650: URL: https://github.com/apache/rocketmq-dashboard/issues/1650
## Problem `RocketMQMetadataProvider#getTopicConsumers` sums per-queue lag values directly. `ConsumerLagResolver` deliberately returns `-1` when a queue's lag is unknown, but direct addition turns mixed results into a plausible number (for example, `10 + (-1) = 9`). If consume stats cannot be read for a group, the fallback also reports `0`, which incorrectly means known zero lag. This hides the unknown state that the RocketMQ 5.0 consumer-lag resolver was introduced to preserve. ## Reproduction 1. Return two queue offsets for a Topic consumer group: one with lag `10`, one with broker/consumer offsets that resolve to unknown (`-1`). 2. Call `getTopicConsumers`. 3. The group summary reports `9` instead of `-1`. A stats-read exception similarly produces `0` instead of `-1`. ## Expected behavior - If any queue lag is unknown, the aggregate Topic consumer lag remains `-1`. - If group consume stats cannot be read, the fallback summary uses `-1` rather than fabricating zero lag. - Fully known queue lags continue to sum normally. -- 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]
