Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message maybe cleaned by cleanExpiredMsg service, while the message has not been consumed. #1034

Closed
humkum opened this issue Apr 14, 2023 · 2 comments · Fixed by #1035
Closed
Labels
discuss Something undering disscussing
Milestone

Comments

@humkum
Copy link
Contributor

humkum commented Apr 14, 2023

Consume startTime was set in message properties when the message was in consume logic.
If the message in process queue has not been consumed & the clean expired message routine would remove these messages and send it back to retry topic. As follows:

QzuBsAWsyp

@francisoliverlee
Copy link
Member

IMO for now it means messages not consumed cause of timeout should be sent to retry topic. what do you think ?

@cserwen
Copy link
Member

cserwen commented Apr 27, 2023

看起来是消息刚被拉取到了客户端,但由于消息还未被消费,因此没有设置开始消费时间戳,被清理消费超时的任务给放入重试队列,实际上远远没有达到消费超时时间,容易造成消费重复 @francisoliverlee

@cserwen cserwen added this to the 2.1.2 milestone Apr 27, 2023
cserwen pushed a commit that referenced this issue Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Something undering disscussing
Projects
None yet
3 participants