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

[GitBox <gi...@apache.org>]

michaeljmarshall commented on issue #5881:
URL: https://github.com/apache/pulsar/issues/5881#issuecomment-1211570827

   > 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.
   
   The DLQ implementation is only triggered after the client negatively acknowledges a message, the client calls `redeliverUnacknowledgedMessages`, or the ack timeout expires. Therefore, changing when the count is incremented does not solve this problem for the DLQ implementation.
   
   I would like to return to the original behavior for incrementing the DLQ counter (`redeliveryCount`). Here is a dev mailing list discussion https://lists.apache.org/thread/ts9d6zbtlz3y5xtv7p0c3dslk0vljpj2 and here is the PR to revert the behavior https://github.com/apache/pulsar/pull/17060.
   
   Please feel free to respond with comments. Thanks.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org