ci(flink-image): abort throttled archive.apache.org downloads instead of hanging - #221
Merged
Merged
Conversation
… of hanging The flink binary tarball comes from archive.apache.org, which throttles aggressively; a wedged connection produces zero curl output and the image build hung 10-30 min on four flink-smoke runs today (#213/#218/#219/#220 lanes) — always right after the ca-certificates layer, i.e. at this curl. Speed guard: abort any transfer below 64 KB/s for 60 s, retry up to 5 times; combined with the bounded build from #220 the lane now self-heals. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DORA Metrics
|
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
2 participants
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.
Root cause of the flink-smoke 30-min hangs (#213/#218/#219 lanes, and the 2x10-min bounded stalls on the #220 lane): the flink binary tarball download from archive.apache.org — a server that throttles aggressively — ran as
curl -fsSLwith no timeouts and no progress output. A throttled/wedged connection therefore produced zero output right after the ca-certificates layer and hung until something killed the job.Fix:
--connect-timeout 30 --speed-limit 65536 --speed-time 60 --retry 5 --retry-all-errorson the archive.apache.org and Maven Central downloads — any transfer crawling below 64 KB/s for 60 s aborts and retries. Combined with the bounded build + retry from #220, the lane now self-heals from mirror throttling instead of hanging or failing the whole job.This PR's own flink-smoke check exercises exactly this build path.
🤖 Generated with Claude Code