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

   ### 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
   
   SUSE Linux Enterprise Server 12 SP
   
   ### RocketMQ version
   
   4.9.3
   
   ### JDK Version
   
   1.8.0_362
   
   ### Describe the Bug
   
   slave get many warnings "found a illegal magic code"
   
   We use m-s mq cluster, and master's config is
   "brokerRole=SYNC_MASTER
   flushDiskType=ASYNC_FLUSH" .
   
   Rmq version is 4.9.3. I guess this issue is also exist in apache rmq.
   
   One day master's server was os crash , then we fixed the os and restarted 
master broker. We found slave can sync commitlog file but can not update 
consume queue file. The warining is "found a illegal magic code 0x66666". The 
log is always print this warning.
   
   ### Steps to Reproduce
   
   One day master's server was os crash , then we fixed the os and restarted 
master broker. We found slave can sync commitlog file but can not update 
consume queue file. The warining is "found a illegal magic code 0x66666". The 
log is always print this warning.
   
   ### What Did You Expect to See?
   
   The warining is "found a illegal magic code 0x66666". The log is always 
print this warning.
   
   ### What Did You See Instead?
   
    slave can sync commitlog file and can update consume queue file
   
   ### 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: [email protected]

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

Reply via email to