[Bug] Pop revive service may get stuck in infinitely retry of old epoch messages when a topic is deleted then recreated

[redlsz]

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

all

RocketMQ version

develop

JDK Version

8

Describe the Bug

The request offset of old epoch is bigger than the current max queue offset. And the final impact is infinitely retry or end with reviving wrong messages.

Steps to Reproduce

See bug description

What Did You Expect to See?

See bug description

What Did You See Instead?

See bug description

Additional Context

No response

[lizhimins]

这里应该是没区分获取消息失败还是位点无效

[redlsz]

这里应该是没区分获取消息失败还是位点无效

是的，我理解获取消息返回 OFFSET_OVERFLOW_ONE 和 OFFSET_OVERFLOW_BADLY 时可以跳过了
另外为了避免重试旧的消息或丢消息(#7914) ，revive 流程可以根据 popTime 和最大长轮询时间做一个校验?

[redlsz]

Fixed at #8475