-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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]: Messages are not ACK on Pubsub starting Beam 2.52.0 on Flink Runner in detached mode #29902
Comments
Also, it might be good to add the |
there wasn't much changes for flink runner between Beam 2.51.0 and 2.52.0 except for #28614, which known to have caused a couple of flaky tests and then fixed later. Is attached mode works fine? |
Impossible to test on my end with the setup I have. When running through |
Similar thing happening with AWS SqsIO after update to 2.52. It seems that #28614 replaced |
CC: @jto who has been quite responsive. Would appreciate if you can share some ideas about fixing #29902 (comment) |
Move to P1 as this essentially breaking streaming FlinkRunner. If it's not fixed in the next release I would suggest revert #28614 and related changes. @noster-dev @gfalcone are you able to test that reverting that change would resolve the issue? |
I can confirm that reverting to 2.51 fixes the problem. Tomorrow I will try to test it on 2.52 with #28614 reverted |
Hi, are there any updates to this issue? I'm facing a potentially similar issue with Kafka source not committing offsets back even though commitsOffsetsInFinalize is true and checkpointing is enabled. Committing offsets works in Beam v2.51.0. |
Hey there! |
Yes, also related to missing |
What happened?
Hello !
I have a streaming job processing messages from Pub/Sub that does not work anymore using Beam 2.52.0 with Flink Runner (in detached mode)
The pipeline works fine in Beam 2.51.0
Here is the code of the pipeline :
With the pom.xml :
And the associated configuration :
Here is the screenshot from Google Cloud Console showing that messages are never acked :
Thank you for your help :)
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: