-
Notifications
You must be signed in to change notification settings - Fork 27
[Rust] Fix Arrow failed-enqueue finalization #738
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
Merged
nikolaobradovic-db
merged 3 commits into
main
from
nikola-obradovic_data/zerobus/arrow_fix_failed_enque_rec_disabled
Aug 17, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should we bound the wait with
flush_timeout_ms?wait_for_offset_internalis bounded byflush_timeout_ms, but this path loops untilCloseState::Finalized. The empty-targetflush()branch and theOpenplusadmission_closedarm ofclose_internalhave the same unbounded wait. If the supervisor never reachesfinish(),ingest_batchhangs a caller ingest loop.The rustdoc says this call returns the request-stream error, but that is only true on
Err. TheOk(())arm synthesizesStatus::internal("Failed to send batch"), while the supervisor's send failure isStatus::unavailablewithFlight request stream closed while sending. ThatOkarm looks unreachable after theadmission_closedclaim, but if we keep it, could we still surface whatever is onserver_error_rxinstead of a generic internal?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.
We should not use flush_timeout_ms here because this is terminal lifecycle coordination, not an ACK/flush wait. Returning on timeout could expose an incompletely finalized stream, make get_unacked_batches() temporarily invalid, and hide the real request-stream error. The wait is cancellation-safe, and finalization continues independently through the supervisor/reaper.
It is possible to do it by adding yet another complex state machine, by aborting the supervisor and awaiting the reaper, which I would rather skip at the cost of having a hang in case the supervisor deadlocks(for now).
I will just make a small change to preserve the terminal error.