This message was deleted.
# generals
Slackbot
10/11/2023, 1:04 PMThis message was deleted.
m
Mickael
10/11/2023, 2:46 PMHi Ivan, we had the same issue and we assumed it is a feature as well. Your scenerio is describe as Scenario 3 here:
https://streamnative.io/blog/apache-pulsar-client-application-best-practices
👍 1
Mickael
10/11/2023, 2:49 PMAs described here:
https://pulsar.apache.org/docs/next/concepts-messaging/#preserving-order-of-processing
A solution consists in enabling
allowOutOfOrderDelivery👍 1
i
Ivan S Onde
10/12/2023, 5:37 AM@Mickael Thank you for the great articles!
Could you please elaborate on the solution? Why is message 3 halted since message 1 has was sent before and the ordering between message 1 and message 3 preserves?
m
Mickael
10/12/2023, 2:46 PMAre message 1 and 3 having the same key? If yes, it could be that message 3 cannot be delivered to consumer 1 as consumer 2 as not yet ack message 1. The key remains assigned to consumer 2 and cannot be given back to consumer 1
i
Ivan S Onde
10/13/2023, 6:15 AMNo, message 1 and message 3 have different keys.
If the key was the same - I agree with you, it's sensible to block such a message.
2 Views