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
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.
The text was updated successfully, but these errors were encountered:
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.
+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!
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.
The text was updated successfully, but these errors were encountered: