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

Maximum tries for redelivery tracker #4

Open
shubhamDhoble opened this issue Dec 5, 2017 · 2 comments
Open

Maximum tries for redelivery tracker #4

shubhamDhoble opened this issue Dec 5, 2017 · 2 comments

Comments

@shubhamDhoble
Copy link

Hi,
Great work, Just wanted to enquire about any way to restrict number of retries for redelivery a message to a queue. So in case the client is down parmanently, the topic would not populate beyond certain fixed number of redelivered messages.

@adamw
Copy link
Member

adamw commented Dec 6, 2017

Thanks, that's not currently implemented, but would be an easy modification: the RedeliveryTracker should be additionally parametrized with a function which transforms the message before redelivery. That would have the possibility to add and increment a delivery counter. Messages which have too many redeliveries could then be discarded by the application logic, or maybe even automatically directed to a DLQ by the RedeliveryTracker.

@smcallister
Copy link

+1 for this suggestion. For my use case, I'd like to use Kafka as a message queue for dispatching requests to remote endpoints. If an endpoint is down for a significant (or even indefinite) period of time, it would be nice to have a way to stop retrying and move the message to a DLQ.

Otherwise, this technology is awesome and simplifies some previously complex use cases when using Kafka!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants