You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/12/17 16:22:03 UTC

[GitHub] [pulsar] frejonb commented on issue #5881: Redelivery count implementation can bring down all the consumers

frejonb commented on issue #5881: Redelivery count implementation can bring down all the consumers 
URL: https://github.com/apache/pulsar/issues/5881#issuecomment-566637265
 
 
   @codelipenghui But doesn't DLQ suffer the same problem that I describe? A "bad" message will never go to the DLQ since it kills consumers before the redelivery count goes up.
   
   If the redelivery count is increased when the message is received, can't we change the implementation of DLQ so it checks whether the message should go to DLQ:
   1. after ack timeout
   1. after nack
   1. before receiving the message (in case neither 1. or 2. triggered)

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services