GitHub user Jason918 added a comment to the discussion: Need max redelivery count at message level.
> 1. If I just set` enableRetry(true)`, how much time does it wait to confirm > whether an acknowledgement is done or not and replay the message? Because we > are not using any timeout here. IIUC, it won't replay unless the consumer reconnects, e.g. consumer restart or broker restarts. > * Even If I set `maxRedeliverCount(1000)` since I am manually sending the > message to DLQ using my own producer based on max retries using my policy for > each message, how will the message get ack'ed/removed from the retry-queue? You acked it just like it's from main-queue. Internally, client will ack the message from main-queue once it's sent to retry queue. > If i do `consumer.acknowledge(msg);` after sending to DLQ, does it remove > from main queue or retry-queue? Yes. > 3\. We are processing millions of requests in a day, does this scale well? It's ~10 message/second on average, quite small for pulsar actually, which can achieve 1 million msg/second. GitHub link: https://github.com/apache/pulsar/discussions/17626#discussioncomment-3691988 ---- This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
