xdkxlk opened a new issue, #6690: URL: https://github.com/apache/rocketmq/issues/6690
### Is Your Feature Request Related to a Problem? Please Describe It <!-- A clear and concise description of what the problem is. --> For pop orderly, when we pop some messages from a message queue, this queue will be locked during invisible time. During this time period, the message will not be visible to other consumers. However, in the event of an error such as a network disruption, the broker may mistakenly assume that some messages have been sent to the client when in fact they have not been received. In such cases, the messages can only be re-consumed after the invisible time has elapsed. This will lead to message delay. ### Describe the Solution You'd Like <!-- A clear and concise description of what you want to happen. --> We can introduce a new parameter `attemptId` in `PopMessageRequestHeader`. When the broker detects that the attemptId is same as the previous attemptId, this request can obtain the lock, even during the invisible time. If a client encounters any network exceptions, it should retry to pop message with the same `attemptId`. ### Describe Alternatives You've Considered <!-- A clear and concise description of any alternative solutions or features you've considered. --> ### Additional Context <!-- Add any other context or screenshots about the feature request here. --> - [ ] Support reentrant pop orderly for broker - [ ] Support reentrant orderly consumption for proxy - [ ] Support reentrant orderly consumption for PushConsumer of PopMode -- 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]
