apache / eventmesh

EventMesh is a new generation serverless event middleware for building distributed event-driven applications.
https://eventmesh.apache.org/
Apache License 2.0
1.62k stars 640 forks source link

[Enhancement] Implement retry consuming based on Pulsar message middleware #4897

Open HarshSawarkar opened 6 months ago

HarshSawarkar commented 6 months ago

Search before asking

Enhancement Request

This issue aims to implement retry consuming based on Pulsar middleware

Describe the solution you'd like

Implement a retry consuming based on Pulsar

Are you willing to submit PR?

Code of Conduct

github-actions[bot] commented 6 months ago

Welcome to the Apache EventMesh community!! We are glad that you are contributing by opening this issue. :D

Please make sure to include all the relevant context. We will be here shortly.

If you are interested in contributing to our project, please let us know! You can check out our contributing guide on contributing to EventMesh.

Want to get closer to the community?

WeChat Assistant WeChat Public Account Slack
Join Slack Chat
Mailing Lists: Name Description Subscribe Unsubscribe Archive
Users User support and questions mailing list Subscribe Unsubscribe Mail Archives
Development Development related discussions Subscribe Unsubscribe Mail Archives
Commits All commits to repositories Subscribe Unsubscribe Mail Archives
Issues Issues or PRs comments and reviews Subscribe Unsubscribe Mail Archives
HarshSawarkar commented 6 months ago

Hi @pandaapo I have creted a PR for this issue.Could you please review it? Here's the link https://github.com/apache/eventmesh/pull/4898

HarshSawarkar commented 6 months ago

In Pulsar the retry queue is triggered by the consumer.ReconsumeLater() method so I tried to leverage it in here.

github-actions[bot] commented 2 months ago

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.