You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Enhancement Request
For the case of message consumption failure, the retry strategy implemented by EventMesh based on RocketMQ currently fully supports the HTTP protocol running mode of EventMesh, and the retry under the grpc and tcp protocols is waiting to be consummated.
@pandaapo Hi, I am new to the Eventmesh community. But I am interested in this task. If you can suggest some modules to explore then it will be helpful.
You can refer to some of the content in this PR #4544. This pull request mainly implements the retry strategy based on RocketMQ, and also completes the use of this strategy under HTTP protocol. You can complete the use of this strategy for gRPC protocol, or TCP protocol, or both.
I've noticed that the retry strategies in the retry module directly invoke the production methods of the storage module. Is it necessary to add support for the gRPC storage module in RocketMQ 5.x to address this issue?
Search before asking
Enhancement Request
For the case of message consumption failure, the retry strategy implemented by EventMesh based on RocketMQ currently fully supports the HTTP protocol running mode of EventMesh, and the retry under the grpc and tcp protocols is waiting to be consummated.
对于消息消费失败的情况,目前EventMesh基于RocketMQ实现的重试策略,完整地支持EventMesh的http协议运行方式,grpc协议和tcp协议下的这种重试等待完善。
Describe the solution you'd like
task list
Welcome to claim the task you are interested in and create corresponding sub issue.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: