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

   ### 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
   
   Ubuntu 22.04.2 LTS
   
   ### RocketMQ version
   
   5.1.1
   
   ### JDK Version
   
   openjdk version "1.8.0_362"
   OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~22.04-b09)
   OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
   
   ### Describe the Bug
   
   when broker is killed -9,  sometimes will restart fail,  report "0 length 
not matched message store config value" in store.log
   
![image](https://github.com/apache/rocketmq/assets/14816818/8935f485-43a4-4890-91f9-27ef0b1d4a16)
   
   
   
   ### Steps to Reproduce
   
   kill -9 broker process. and then restart
   
   ### What Did You Expect to See?
   
   restart success
   
   ### What Did You See Instead?
   
   report "0 length not matched message store config value" in store.log
   
![image](https://github.com/apache/rocketmq/assets/14816818/8935f485-43a4-4890-91f9-27ef0b1d4a16)
   
   
   
   ### Additional Context
   
   
![image](https://github.com/apache/rocketmq/assets/14816818/c75d06bc-68ef-40f8-964e-4e32d57c5249)
   
   if broker is killed before fileChannel.map, then file size is 0.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to