Suhas Karanth
06/10/2025, 4:41 AMRunLLM
06/10/2025, 4:41 AMReconsumeLater are persisted to the retry letter topic; NACKed messages use the client-side cache and are not persisted to BookKeeper by default. This matches the behavior described in the documentation for Java clients and is confirmed for Go as well according to Pulsar Go client issue #603 and Pulsar Go client PR #359.
Would you like more detail on how to configure or use these features in the Go client?
Sources:
- Pulsar Go client PR #359
- Pulsar Go client issue #603 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Suhas Karanth
06/10/2025, 5:37 AMRunLLM
06/10/2025, 5:37 AMSuhas Karanth
06/10/2025, 5:53 AMReconsumeLater?RunLLM
06/10/2025, 5:53 AMReconsumeLater. However, if a negative value is provided, it is set to zero internally, and the delay is specified as a time.Duration in Go, which is a 64-bit integer nanoseconds value (consumer_impl.go). There is no explicit upper bound enforced in the Go client, but extremely large values may be limited by system or broker configuration.
Would you like more detail on how delays are handled or any broker-side implications?
Sources:
- consumer_impl.go 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Suhas Karanth
06/10/2025, 5:57 AMReconsumeLater for a message, do I need to acknowledge it as well?RunLLM
06/10/2025, 5:57 AMReconsumeLater for a message, you do not need to acknowledge it. The message will be scheduled for redelivery after the specified delay, and acknowledgment is not required or expected in this case (Pulsar Go client issue #603, PR #359).
Would you like more detail on the message lifecycle when using ReconsumeLater?
Sources:
- Pulsar Go client issue #603 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Suhas Karanth
06/10/2025, 6:01 AMRunLLM
06/10/2025, 6:01 AMReconsumeLater, the original message is not acknowledged immediately. Instead, the message is republished to the retry letter topic with updated properties (such as retry count), and the consumer automatically subscribes to both the original and retry topics. The message is only acknowledged on the original topic and subscription when it is successfully processed and explicitly acknowledged by the consumer after redelivery (Pulsar 4.0.x concepts-messaging).
Would you like more detail on the flow between retry, dead letter, and original topics?
Sources:
- Pulsar 4.0.x concepts-messaging 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Suhas Karanth
06/10/2025, 6:30 AMMessage.RedeliveryCount?RunLLM
06/10/2025, 6:30 AMMessage.RedeliveryCount will be 0 (Pulsar Go client source, Pulsar concepts-messaging docs).
Would you like more detail on how this value changes with redeliveries?
Sources:
- Pulsar Go client source
- Pulsar concepts-messaging docs 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.