You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2020/05/20 19:39:21 UTC

[GitHub] [rocketmq] imaffe edited a comment on issue #1960: TopicStatusSubCommand get min offset is inaccurate

imaffe edited a comment on issue #1960:
URL: https://github.com/apache/rocketmq/issues/1960#issuecomment-631683795


    Does this bug apply to all topics or just the dead letter topic ?
   
   Because I noticed when the scheduled service clears commitLogs periodically, it will actually update the minOffset in corresponding consume queues as well. 
   ```
           this.scheduledExecutorService.scheduleAtFixedRate(new Runnable() {
               @Override
               public void run() {
                   DefaultMessageStore.this.cleanFilesPeriodically();
               }
           }, 1000 * 60, this.messageStoreConfig.getCleanResourceInterval(), TimeUnit.MILLISECONDS);
   
   ... 
   
       private void cleanFilesPeriodically() {
           this.cleanCommitLogService.run();
           this.cleanConsumeQueueService.run();
       }
   
   ```
   If it turns out this bug was caused by existing logic we might just find out what's going on in previous logic.
   
   I might get this wrong so I would appreciate much if you could provide more details on this, thanks ~


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org