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/11/04 05:31:30 UTC

[GitHub] [pulsar] zymap commented on issue #5344: In Pulsar client, the effective value of NackRedeliveryDelay is about 1/3 of its specified value

zymap commented on issue #5344: In Pulsar client, the effective value of NackRedeliveryDelay is about 1/3 of its specified value
URL: https://github.com/apache/pulsar/issues/5344#issuecomment-549228474
 
 
   Hi @Jesse-Zhang-Bose . I think that is the right process.
   
   There are two variables of NackRedelivery. One is `NackRedeliveryDelay`, another is `TimeInterval`.
   
   The `NackRedeliverDelay` is the message should redelivery after how long. And the `TimeInterval` is the scheduler time interval.
   
   The scheduler will check is there any messages that need to redeliver. And it will be scheduled with the time gap specified by `TimeInterval`. The `TimeInterval` is set to 1/3 `NackRedeliveryDelay`. So you will see it retry after 1/3 of  nack redelivery delay.  
   
   You can see the implementation of the Nack at here https://github.com/apache/pulsar/blob/master/pulsar-client-cpp/lib/NegativeAcksTracker.cc
   
   It implemented as same as java   https://github.com/apache/pulsar/blob/7275d53af463ed3526d93a88d27d278802425a4d/pulsar-client/src/main/java/org/apache/pulsar/client/impl/NegativeAcksTracker.java#L54

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