You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/06/25 08:16:43 UTC

[GitHub] [pulsar-dotpulsar] dionjansen commented on issue #45: Support - Consumer.NegativeAcknowledge

dionjansen commented on issue #45:
URL: https://github.com/apache/pulsar-dotpulsar/issues/45#issuecomment-649355282


   From what I can tell both the Java and C++ clients use a client sided tracker to keep track of negatively acknowledged messages add by the [Consumer. negativeAcknowledge](https://github.com/apache/pulsar/blob/6926180966f45eb9c1499b7f0eb32ea2a1368fd6/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ConsumerImpl.java#L722) in a [NegativeAcksTracker](https://github.com/apache/pulsar/blob/6926180966f45eb9c1499b7f0eb32ea2a1368fd6/pulsar-client/src/main/java/org/apache/pulsar/client/impl/NegativeAcksTracker.java). The tracker is responsible for calling the [RedeliverUnacknowledgedMessages](https://pulsar.apache.org/docs/en/develop-binary-protocol/#command-redeliverunacknowledgedmessages)  consumer command, with those message ids that exceed their respective timeout.
   
   I see there is some interaction with another mechanism required to track unacked messages but this only exists when the client actually sets an AckTimeout (request in #46)


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