[Bug] consumequeue correctMinOffset throws IllegalArgumentException causing startup failure

[woaishixiaoxiao]

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

centos7

RocketMQ version

rocketmq-all-5.3.3 Latest and develop

JDK Version

JDK 1.8

Describe the Bug

Steps to Reproduce

1. the last mappfile in the A consumequeue is empty (this is possible because of asynchronous refresh)
2. commitlog is configured with async-flush and sync-master, commitlog messages which build A consumequeue lost during restart
3. broker restart will not truncate(truncateDirtyLogicFiles) the last empty A consuequeue mappflile
4. correctMinOffset in recoverTopicQueueTable will throw IllegalArgumentException and restart failed

What Did You Expect to See?

An empty consumequeue will not cause broker restart failure

What Did You See Instead?

broker restart failure

Additional Context

No response