[Bug] Broker dispatch messages despite a message with the same key is unack

[TTMickael]

Search before asking

• 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!

[poorbarcode]

@TTMickael

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

[TTMickael]

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?

[github-actions]

The issue had no activity for 30 days, mark with Stale label.

[Denovo1998]

@TTMickael @poorbarcode
Maybe the first consumer without ack message was closed after sending a second message with the same key?