Repository navigation
Design delayed retries for throttled input downloads - #2955
Open
MarcusSorealheis wants to merge 2 commits into
Open
MarcusSorealheis wants to merge 2 commits into
MarcusSorealheis wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
What and why
Proposes a scheduler delay after input preparation exhausts its deadline on a confirmed upstream throttle. The design covers typed throttle propagation, persisted retry eligibility, result acknowledgments, bounded retry budgets, and a preference for a suitable worker that may retain input data.
Addresses the design item TRA-1471. It accounts for the existing local input retries and reservation holds, and the stream protocol's lack of durable result acknowledgment. Implementation order, mixed-version rollout, rollback, and acceptance checks are included. Runtime behavior and configuration remain unchanged.
How was this verified?
Checked the proposal against the current input preparation, retry, worker stream, and scheduler code, including the result-delivery and execution-ceiling decisions in #2923 and #2925. All relative source links resolve. Repository pre-commit hooks, including Vale and typos, passed for the new document.
No executable code changed; the proposed protocol and scheduling behavior still require implementation and tests.
Risk
Documentation only. The delay defaults are proposals for review. Enabling the future behavior requires result acknowledgment and compatible deferred-state readers on every scheduler sharing the database.
AI assistance
Automated assistance was used to draft the design and run the listed checks.
This change is