lizhimins opened a new issue, #8007: URL: https://github.com/apache/rocketmq/issues/8007
### 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 5.10.112-005.ali5000.alios7.x86_64 ### RocketMQ version develop version: 5.1.4 ### JDK Version JDK11 ### Describe the Bug The last index file should not be deleted when the broker recovers abnormally.  ### Steps to Reproduce - First, send more than 3GB of data to the broker, then terminate the broker process using "kill -9" and restart it. - The broker will enter an abnormal recovery process and delete the last index file. - We can't query message by message uniqueKey which earliest send, it would return failed. ### What Did You Expect to See? The last index file should not be deleted when the broker recovers abnormally ### What Did You See Instead? The last index file should not be deleted when the broker recovers abnormally ### 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-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
