Skip to content

[Dataflow Streaming] [Multi Key] Drop failed work in BoundedQueueExecutor::pollWork#38920

Open
arunpandianp wants to merge 2 commits into
apache:masterfrom
arunpandianp:multikey_queue_filter_failed
Open

[Dataflow Streaming] [Multi Key] Drop failed work in BoundedQueueExecutor::pollWork#38920
arunpandianp wants to merge 2 commits into
apache:masterfrom
arunpandianp:multikey_queue_filter_failed

Conversation

@arunpandianp

Copy link
Copy Markdown
Contributor

Drop failed work in BoundedQueueExecutor::pollWork before it reaches the harness threads for execution.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 improves the robustness of the BoundedQueueExecutor by ensuring that failed work items are filtered out during the polling process. By identifying and dropping these items before they reach the execution threads, the system avoids unnecessary processing overhead and potential errors associated with failed tasks.

Highlights

  • Failed Work Handling: Updated BoundedQueueExecutor::pollWork to automatically identify and drop failed work items before they are processed by harness threads.
  • Queue Management: Implemented a loop in the polling logic to skip over failed work, ensuring that only valid work is returned for execution.
  • Resource Cleanup: Added explicit handle closure for failed work items to ensure resources are properly released.
New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the 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 counterproductive. 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.

Footnotes

  1. 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.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the BoundedQueueExecutor to continuously poll and drop failed work items, closing their handles, until a valid work item is found or the queue is empty. A corresponding unit test, testPollWorkDropsFailedWork, was added to verify this behavior. The review feedback correctly points out a potential thread leak in the new test if assertions fail before the blocker thread is unblocked and the executor is shut down. It is recommended to wrap the test assertions and execution in a try-finally block to guarantee proper cleanup.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@arunpandianp

Copy link
Copy Markdown
Contributor Author

R: @scwhittle

@github-actions

Copy link
Copy Markdown
Contributor

Assigning reviewers:

R: @Abacn added as fallback since no labels match configuration

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

return null;
}
if (queuedWork.getWork().work().isFailed()) {
queuedWork.getHandle().close();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is just updating the counters, but it is not updating that this key was scheduled for processing. I think that somehow ActiveWorkState.completeWorkAndGetNextWorkForKey needs to be called so that we note that this key is completed and other work for the key can schedule.

Maybe a unit test at a higher level would help verify this behavior is working properly.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching it. Will fix it with a test, after #38814 is merged

@github-actions

Copy link
Copy Markdown
Contributor

Reminder, please take a look at this pr: @Abacn

@github-actions

Copy link
Copy Markdown
Contributor

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @Abacn added as fallback since no labels match configuration

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

@scwhittle

Copy link
Copy Markdown
Contributor

Current status: waiting for other PR to merge to improve tests for this one before merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants