HScarb opened a new pull request, #8754:
URL: https://github.com/apache/rocketmq/pull/8754

   <!-- Please make sure the target branch is right. In most case, the target 
branch should be `develop`. -->
   
   ### Which Issue(s) This PR Fixes
   
   <!-- Please ensure that the related issue has already been created, and 
[link this pull request to that issue using 
keywords](<https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword>)
 to ensure automatic closure. -->
   
   Fixes #8753
   
   ### Brief Description
   
   <!-- Write a brief description for your pull request to help the maintainer 
understand the reasons behind your changes. -->
   Ref: #4568 
   
   ### How Did You Test This Change?
   
   <!-- In order to ensure the code quality of Apache RocketMQ, we expect every 
pull request to have undergone thorough testing. -->
   
   1. Set mappedFileSizeCommitLog to 102400.
   2. Create 3 topics: TopicTest1 TopicTest2 TopicTest3.
   3. Produce 1000 messages to each topic in sequence.
   4. Now we may have 6 CommitLog files, use the RocketMQ admin client to 
delete the first 5 of them.
   5. Use TopicStatus admin command to retrieve TopicTest1's status.
   
   The result is correct:
   
   ```log
   #Broker Name                      #QID  #Min Offset           #Max Offset    
         #Last Updated
   broker-a                          0     250                   250            
         
   broker-a                          1     250                   250            
         
   broker-a                          2     250                   250            
         
   broker-a                          3     250                   250            
         
   ```


-- 
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