[GitHub] [rocketmq] AshleyLiuuuuu commented on issue #3062: Why is the consume offset become less when the timestamp set to “now”?(MQAdmin)

[GitBox <gi...@apache.org>]

AshleyLiuuuuu commented on issue #3062:
URL: https://github.com/apache/rocketmq/issues/3062#issuecomment-881288995


   > First of all, 4.3.0 uses this command resetOffsetByTime, which is indeed the offset of the rollback. And the actual command in the above picture is this resetOffsetByTimeOld, this command is not supported in 4.3.0, and the parameters of the above picture cannot be run with this command, so the author of the above picture changed the source code and ran out.
   > ![image](https://user-images.githubusercontent.com/33314633/125906691-8893b628-15d1-406a-8426-b0d555f3d1af.png)
   
   Hi
   In fact I don't quite understand what you mean, but I found that last year, someone has already noticed this bug, and if you look carefully at the source code will know that either resetOffsetByTime or resetOffsetByTimeOld, the core method to get the specified timestamp offset is always method getOffsetInQueueByTime, and this method I debugged, the timestampOffet will always be smaller than the actual correct consumption offset of 1 unit, so I think it's nothing to do with the version or the commands we use.


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