smallemployees opened a new issue, #7576: URL: https://github.com/apache/rocketmq/issues/7576
### 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 K8s running cluster ### RocketMQ version 4.6.0 ### JDK Version _No response_ ### Describe the Bug After the pod restarts, the consistent startup fails, indicating that the instance has already been running. However, the reason for checking later is that the lock file already exists. Why didn't the cleaning be done during the restart ### Steps to Reproduce Abnormal down of service, causing K8S to pull up the pod ### What Did You Expect to See? Can clear lock files before shutting down ### What Did You See Instead? 重启失败 ### 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
