Repository navigation
fix(rest): retry GET connection failures with bounded backoff - #1272
Merged
JingsongLi merged 2 commits intoNov 1, 2026
Merged
Conversation
XiaoHongbo-Hope
marked this pull request as ready for review
November 1, 2026 14:03
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.
What
Retry REST GET connection failures (including DNS resolution failures) at most
twice, with jittered exponential backoff. Every attempt retains the existing
180-second connect/read timeouts; there is no new whole-request deadline.
Connection retries share the existing GET
attempt limit. The 429/503 policy and POST/DELETE paths are unchanged.
Why
The existing status retry loop returns immediately when reqwest fails before
receiving a response. A transient resolver failure can therefore abort native
catalog planning. This adds bounded tolerance, not a fix for persistent DNS
misconfiguration. No new dependency or configuration is introduced.
Tests
Added deterministic resolver tests for recovery, retry exhaustion, no mutation
retry, and one DNS failure followed by response headers delayed for six seconds.
Existing REST client tests are also included in the run.
cargo fmt --all --checkandgit diff --check: passed.cargo test -p paimon --lib api::rest_client::tests --no-default-features --features storage-memory,storage-fs: 12 passed on head7c44f424, including delayed response headers after DNS recovery.