Skip to content

[Rust][Arrow] Coordinate explicit close with recovery #677

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.

Sign up for GitHub

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

Open
teodordelibasic-db wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[Rust][Arrow] Coordinate explicit close with recovery #677

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4de2584
[Rust] Fix close during Arrow recovery
teodordelibasic-db Aug 5, 2026
45e99e0
[Rust] Preserve close recovery error
teodordelibasic-db Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions rust/NEXT_CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,10 @@
`InvalidArgument` when ACK or recovery deadlines exceed the platform
monotonic-clock range. Server-advertised graceful-rotation periods are capped
at one year.
- Fixed Arrow Flight explicit close during recovery. Close now interrupts recovery
backoff, connection setup, ready-signal waiting, and replay; the supervisor finalizes
exactly once, preserves real peer/authentication errors, and retains only the correct
unacknowledged batch suffixes.
- Fixed Arrow Flight recovery sender lifetime: replacement senders are now published
only after pending replay succeeds, while initial supervisor handoff and failed or
cancelled replay promptly drop redundant senders instead of retaining incomplete
Expand Down
Loading
Loading