Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
1 of 2 tasks
TTMickael opened this issue Jul 28, 2023 · 4 comments · Fixed by #23352
Closed
1 of 2 tasks

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

TTMickael opened this issue Jul 28, 2023 · 4 comments · Fixed by #23352
Labels
Stale type/bug The PR fixed a bug or issue reported a bug

Comments

@TTMickael
Copy link

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!
@TTMickael TTMickael added the type/bug The PR fixed a bug or issue reported a bug label Jul 28, 2023
@TTMickael TTMickael changed the title [Bug] [Bug] Messages are sent despite a message with the same key is not acked Jul 28, 2023
@TTMickael 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
@poorbarcode
Copy link
Contributor

@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
Copy link
Author

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
Copy link

github-actions bot commented Sep 9, 2023

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

@github-actions github-actions bot added the Stale label Sep 9, 2023
@Denovo1998
Copy link
Contributor

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

CleanShot 2023-11-18 at 23 22 31@2x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants