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 2021/10/14 13:20:04 UTC

[GitHub] [rocketmq] Git-Yang opened a new issue #3412: [store] nextBeginOffset is greater than maxOffset problem

Git-Yang opened a new issue #3412:
URL: https://github.com/apache/rocketmq/issues/3412


   1. Please describe the issue you observed:
   Background:
   There is only one file in a consumeQueue, and part of the data has expired. As follows：
   ![image](https://user-images.githubusercontent.com/30995057/137322246-a7bb327a-1b1c-44c1-b3ff-0a95b014db30.png)
   - minOffset=0, maxOffset=851686, nextBeginOffset=30000
   ![image](https://user-images.githubusercontent.com/30995057/137322780-30ec5821-3b7e-40d6-a252-5e73f57ef33f.png)
   ![image](https://user-images.githubusercontent.com/30995057/137322871-69b06e2c-683e-493f-b469-35e5753ef004.png)
   
   - Use Go SDK to consume
   ![image](https://user-images.githubusercontent.com/30995057/137323528-a12f87ba-a7f2-4828-a2b3-e9b005d60e2e.png)
   
   
   2. Please tell us about your environment:
   - RocketMQ 4.8
   - Go SDK 2.1.0
   
   3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
   - RocketMQ:
   ![image](https://user-images.githubusercontent.com/30995057/137323747-0f590bd0-110e-468a-882d-7b8b260e857c.png)
   - Go SDK:
   ISSUE: https://github.com/apache/rocketmq-client-go/issues/731


-- 
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: dev-unsubscribe@rocketmq.apache.org

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

[GitHub] [rocketmq] Git-Yang commented on issue #3412: [store] nextBeginOffset is greater than maxOffset problem

Posted by GitBox <gi...@apache.org>.
Git-Yang commented on issue #3412:
URL: https://github.com/apache/rocketmq/issues/3412#issuecomment-943454065


   > Is the topic directory wrong? It is inconsistent with the topic in the log. And according to the consumeQueue file, minOffset should not be 0
   
   <img width="1409" alt="WechatIMG133" src="https://user-images.githubusercontent.com/30995057/137345808-fa4812cd-b4de-4e0d-90ad-6d53c6b8a9d7.png">
   


-- 
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: dev-unsubscribe@rocketmq.apache.org

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

[GitHub] [rocketmq] Git-Yang commented on issue #3412: [store] nextBeginOffset is greater than maxOffset problem

Posted by GitBox <gi...@apache.org>.
Git-Yang commented on issue #3412:
URL: https://github.com/apache/rocketmq/issues/3412#issuecomment-943442705


   > Is the topic directory wrong? It is inconsistent with the topic in the log. And according to the consumeQueue file, minOffset should not be 0
   
   The wrong topic has been cut, and this problem has appeared on multiple topics at the same time. I will take a break later.
   There is only one consumeQueue file from start to finish. Due to slow production, some data has expired and been deleted. But minOffset is the actual offset of the smallest file of the current consumeQueue.


-- 
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: dev-unsubscribe@rocketmq.apache.org

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

[GitHub] [rocketmq] panzhi33 commented on issue #3412: [store] nextBeginOffset is greater than maxOffset problem

Posted by GitBox <gi...@apache.org>.
panzhi33 commented on issue #3412:
URL: https://github.com/apache/rocketmq/issues/3412#issuecomment-943434830


   Is the topic directory wrong? It is inconsistent with the topic in the log. And according to the consumeQueue file, minOffset should not be 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: dev-unsubscribe@rocketmq.apache.org

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

[GitHub] [rocketmq] Git-Yang commented on issue #3412: [store] nextBeginOffset is greater than maxOffset problem

Posted by GitBox <gi...@apache.org>.
Git-Yang commented on issue #3412:
URL: https://github.com/apache/rocketmq/issues/3412#issuecomment-943457857


   I think the logic of obtaining minOffset from consumeQueue should be removed, and the client chooses according to consumeFromWhere. However, the above problems may still occur when using ConsumeFromFirstOffset, so you need to modify the consumeOffset in nextBeginOffset.


-- 
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: dev-unsubscribe@rocketmq.apache.org

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