[PECOBLR-3984] Add jitter to chunk download retries - #1647
Open
prathamesh-db wants to merge 3 commits into
Open
Conversation
Signed-off-by: Prathamesh Baviskar <prathamesh.baviskar@databricks.com>
Signed-off-by: Prathamesh Baviskar <prathamesh.baviskar@databricks.com>
prathamesh-db
marked this pull request as ready for review
August 21, 2026 05:20
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
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.
Description
Adds equal jitter (750–1,500 ms) to the existing chunk-download retry delay in both batch and streaming paths. This reduces synchronized retry bursts while preserving five attempts and the existing six-second maximum total retry wait.
Jira: https://databricks.atlassian.net/browse/PECOBLR-3984
Testing
Telemetry Errors
DatabricksDriverErrorCodewhere appropriate, and any new code is uniquely numbered and tested.Additional Notes to the Reviewer
The retry count and existing
CHUNK_DOWNLOAD_ERRORtelemetry code are unchanged. This mitigation reduces correlated retries; it does not claim to eliminate every chunk-download failure.This draft PR was generated by the PECO Agent Workflow and then narrowed to the telemetry-backed mitigation above.