You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@rocketmq.apache.org by "majialoong (via GitHub)" <gi...@apache.org> on 2026/09/24 11:46:06 UTC

[I] [Bug] Stale lag time info remains in getLiteGroupInfo after lite topic expired [rocketmq]

majialoong opened a new issue, #11223:
URL: https://github.com/apache/rocketmq/issues/11223

### Before Creating the Bug Report

- [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions).

- [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate.

- [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

### Runtime platform environment

All

### RocketMQ version

5.5.1

### JDK Version

All

### Describe the Bug

When `liteLagLatencyCollectEnable=true`, lag time info is recorded in `LiteConsumerLagCalculator` during lite pop. After a lite topic expires and is deleted by `AbstractLiteLifecycleManager#deleteLmq`, this info is not removed. The stale entry stays in memory until the broker restarts. It keeps showing up in the "TopK by lag time" section of `getLiteGroupInfo`, and it also affects the `earliestUnconsumedTimestamp` metric.

### Steps to Reproduce

1. Enable `liteLagLatencyCollectEnable=true` on the broker.
2. Send messages to a lite topic and consume them. Make sure at least one pop returns a full batch while more messages remain, so a lag time entry is recorded.
3. Stop consuming, and wait for the lite topic to expire and be cleaned up.
4. Run mqadmin `getLiteGroupInfo -g <group> -p <parentTopic>`.

### What Did You Expect to See?

The expired lite topic should not appear in "TopK by lag time", and "Min Unconsumed Timestamp" should not include it.

### What Did You See Instead?

The expired lite topic still appears in "TopK by lag time" with Lag Count 0 and an old UnconsumedTimestamp. "Min Unconsumed Timestamp" keeps growing.

example:
```
mqadmin getLiteGroupInfo -n xxxx:9876 -g LiteTest2 -p LiteTest2

Lite Group Info: [LiteTest2] [LiteTest2]
------TopK by lag count-----
Total Lag Count: 0
NO Lite Topic Lag Count UnconsumedTimestamp

------TopK by lag time------
Min Unconsumed Timestamp: 1790078803829 (171494 s ago)
NO Lite Topic Lag Count UnconsumedTimestamp
1 lite-topic-2 0 2026-09-22 20:06:43,829
```

### Additional Context

_No response_

--
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: commits-unsubscribe@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Bug] Stale lag time info remains in getLiteGroupInfo after lite topic expired [rocketmq]

Posted by "RongtongJin (via GitHub)" <gi...@apache.org>.

RongtongJin closed issue #11223: [Bug] Stale lag time info remains in getLiteGroupInfo after lite topic expired
URL: https://github.com/apache/rocketmq/issues/11223


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org