Skip to content

Conversation

@arunpandianp
Copy link
Contributor

The race is between commit() and stop().
Since it happens only during shutdown, it doesn't affect cloudpath where commiter is not shutdown till the worker shutdown.
directpath is affected since it can shutdown committers all the time.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @arunpandianp, 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 resolves a critical race condition within the StreamingEngineWorkCommitter that could lead to uncommitted work items during stream shutdown, particularly affecting directpath environments. The changes ensure that all commits are properly processed, even when the system is concurrently shutting down, by adjusting the order of operations in the commit() method and explicitly draining the commit queue. A new, comprehensive test has been added to validate this fix under concurrent conditions, significantly improving the reliability of the streaming engine's commit mechanism.

Highlights

  • Race Condition Fix: Addressed a race condition between the commit() and stop() methods within the StreamingEngineWorkCommitter during stream shutdown, specifically impacting directpath executions.
  • Commit Handling during Shutdown: Modified the commit() method to ensure that work items are added to the commit queue before checking if the committer is shutting down. If shutdown is in progress, drainCommitQueue() is explicitly called to process any newly added commits, preventing them from being orphaned.
  • New Concurrency Test: Introduced a new test case, testStop_drainsCommitQueue_concurrentCommit, which simulates concurrent commit() calls during a shutdown sequence to verify that the commit queue is correctly drained under these conditions.
  • Test Robustness Improvement: Enhanced the waitForExpectedSetSize utility method in the test suite by adding a timeout, making tests more robust against indefinite waits.
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 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

  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.

@arunpandianp
Copy link
Contributor Author

R: @scwhittle @parveensania

@github-actions
Copy link
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

@scwhittle scwhittle merged commit 3516b5d into apache:master Dec 16, 2025
15 checks passed
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