You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched in the issues and found nothing similar.
Version
3.0.0
Minimal reproduce step
Have a partitioned topic
Create a Key_Shared subscription
Produce one message with a key X
Consume one message with the key X but do never ack it
Produce a second message with a key X
What did you expect to see?
The second message is not pushed by the broker
What did you see instead?
The second message is consumed
Anything else?
This behavior has been observed after migrating from 2.10.1 to 3.0.0
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
TTMickael
changed the title
[Bug]
[Bug] Messages are sent despite a message with the same key is not acked
Jul 28, 2023
TTMickael
changed the title
[Bug] Messages are sent despite a message with the same key is not acked
[Bug] Broker dispatch messages despite a message with the same key is unack
Jul 28, 2023
Have a partitioned topic
Create a Key_Shared subscription
Produce one message with a key X
Consume one message with the key X but do never ack it
Produce a second message with a key X
Is there only one consumer to consume messages? If yes, it is an expected behavior
We have 2 consumers for this subscription. I'm expecting in any case that messages with the same key won't be dispatched to ensure the order of delivery unless the unacked message get acked. Am I wrong?
Search before asking
Version
3.0.0
Minimal reproduce step
Have a partitioned topic
Create a Key_Shared subscription
Produce one message with a key X
Consume one message with the key X but do never ack it
Produce a second message with a key X
What did you expect to see?
The second message is not pushed by the broker
What did you see instead?
The second message is consumed
Anything else?
This behavior has been observed after migrating from 2.10.1 to 3.0.0
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: