NiuBlibing commented on issue #23944: URL: https://github.com/apache/pulsar/issues/23944#issuecomment-2709243780
> > Currently, the message redelivery count (RedeliveryCount) only increases when the client actively calls the redeliver method [#18239](https://github.com/apache/pulsar/issues/18239). > > [@NiuBlibing](https://github.com/NiuBlibing) > > It’s partially correct. You can enable [ackTimeout](https://github.com/apache/pulsar/blob/branch-3.0/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ConsumerBuilder.java#L200) on the consumer. Once the consumer returns a message from the receive method, the countdown starts. A background [task](https://github.com/apache/pulsar/blob/branch-3.0/pulsar-client/src/main/java/org/apache/pulsar/client/impl/UnAckedMessageTracker.java) runs periodically to redeliver messages that exceed the ackTimeout. For an instance: the application thread which processing message may get stuck on deadlock or other issues, thus it may have no chance to call negativeAck to redeliver this message to other consumer. Yeah, depending on client is not full reliable for these cases. -- 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-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
