feat: expose the reclaim I/O timeout - #54
Merged
Merged
Conversation
leiysky
force-pushed
the
dev/reclaim-io-timeout
branch
from
September 16, 2026 05:18
d9f67a6 to
c5c0caf
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Background reclaim reads currently share the fixed five-second I/O deadline. Add
RuntimeOptions::reclaim_io_timeoutso deployments can allow longer reclaim reads without changing foreground read/write deadlines. The default remains five seconds, and cancellation and cache-failure behavior are unchanged.Validate positive, representable deadlines and document the shutdown and free-capacity tradeoffs. Complete
RuntimeOptionsliterals must supply the new field or use..RuntimeOptions::default().Validation
cargo x checkcargo x test, including completion after the original five-second deadline, configured timeout buffer ownership, and invalid configuration coveragecargo x lint