GitHub user Jason918 added a comment to the discussion: How to avoid repeated consumption in Durable subscription?
> Every time, it is successfully ACKed (is the ACK status information saved > locally?) Not likely, client `ack` need RPC to be persisted to broker. > After restarting the Pulsar and consumers, they will continue to consume at > the last location. In this way, repeated consumption occurs, > > How to avoid it? Are you talking about exactly-once message delivery? Normally, we don't need it. The best practice would be implement idempotent message process at consumer side. If you are talking about minimizing message duplication, it's another story. GitHub link: https://github.com/apache/pulsar/discussions/18170#discussioncomment-3947849 ---- This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
