zbentley commented on issue #8722: URL: https://github.com/apache/pulsar/issues/8722#issuecomment-1126281140
The feature @asgeirrr describes would be incredibly useful for us. One or both of two things (the first probably easier than the second to implement) would be ideal: - Redelivery count to be provided on a per-subscription basis, rather than on a per-message basis. I.e. if consumer A connects on subscription X, gets message 123, then crashes before acking it, consumer B (A's replacement) would see a positive redelivery count when it gets message 123. - Redelivery count to be durably persisted such that even when topics move between brokers, or brokers/bookies fail, the redelivery count number increments every time a message is delivered on a subscription. I'd be willing to trade a substantial slowdown in message delivery/ack processing for this. Durability of redeliveries would enable some really strong guarantees in our consumers around whether there's a risk that multiple instances of consumer code are seeing the same messages at the same time. -- 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]
