imqishi commented on issue #217: URL: https://github.com/apache/pulsar-client-go/issues/217#issuecomment-1954033612
> The ack timeout referred here is not the timeout on the ack operation, rather the timeout on the application processing a message. > > Regardless, it was a mistake to add in Java API, and that’s why we didn’t add it in the new Go API. > > Negative acks are better because they convey the application intention on the outcome of processing a message. > > There’s no context or timeout on the ack/nack operations because these happen in background. > > If these fail, the message will be resent and the application will have the chance to ack/nack again. hi, I want to know if there's no ack-timeout and consume exit without nack, when will the message be resent? If there's situation a long process message cause multiple retry? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
