-
Notifications
You must be signed in to change notification settings - Fork 4.4k
[KafkaIO] Exit the poll loop in ReadFromKafkaDoFn after consumerPollingTimeout has elapsed #36029
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @sjvanrossum, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request addresses a potential starvation issue in the KafkaIO connector's ReadFromKafkaDoFn where the processElement method could continuously poll for records without yielding to the Beam runner. The changes ensure that the polling loop respects the consumerPollingTimeout, allowing the Splittable DoFn to periodically yield control, thereby improving the responsiveness and stability of Kafka-consuming Beam pipelines.
Highlights
- Prevent indefinite polling: The ReadFromKafkaDoFn's poll loop now exits after consumerPollingTimeout has elapsed, preventing it from running continuously without yielding to the runner, even when records are constantly arriving.
- Improved yielding behavior: By ensuring the poll loop terminates within the specified timeout, the SDF (Splittable DoFn) can yield control back to the Beam runner, improving overall pipeline stability and resource management.
- Explicit ProcessContinuation: The processElement method now explicitly returns ProcessContinuation.resume(), ensuring the runner is informed to continue processing the element.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
Good bot. |
You're welcome! I'm glad I could be of assistance. Let me know if you have any more questions or need further review. |
Assigning reviewers: R: @ahmedabu98 for label java. Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
Thank you! We probably need to add an item of existing issue to CHANGES.md as well as website for Beam 2.64.0-2.67.0. Merge this for now. |
ReadFromKafkaDoFn
may keep running without yielding to the runner if records keeps arriving, because this loop can only be escaped when no records have arrived withinconsumerPollingTimeout
or the restriction is truncated.Exiting the loop after
consumerPollingTimeout
has elapsed prevents the SDF from running continuously without yielding to the runner.Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.