pulsar-client-go
pulsar-client-go copied to clipboard
please check Failed by consumer Ack Message ID
https://github.com/apache/pulsar-client-go/blob/b0f328e358d45e822efac164b11dc493bbecfcaa/pulsar/consumer_impl.go#L435
The current Ack command has no return value. If the ack fails, the message will continue to be stored in the backlog on the broker side, and the message will not be lost.
After the 2.8.0 version, we introduced the transaction function, here we added response to Ack's Command
The current Ack command has no return value. If the ack fails, the message will continue to be stored in the backlog on the broker side, and the message will not be lost.
After the 2.8.0 version, we introduced the transaction function, here we added response to Ack's Command
-
If the client is deployed in k8s, then after the client ACK, restarting will cause message duplication (need the client to handle idempotence?)
-
How to guarantee exactly-once?
Under normal use (no transaction) , the semantics is at least once @Liberxue