Retry storage operation on idle connection error during raw file uploads#7368
Draft
ddl-rliu wants to merge 2 commits into
Draft
Retry storage operation on idle connection error during raw file uploads#7368ddl-rliu wants to merge 2 commits into
ddl-rliu wants to merge 2 commits into
Conversation
ddl-rliu
force-pushed
the
rliu.writeraw-retry
branch
3 times, most recently
from
May 14, 2026 00:02
147d1b9 to
ca37329
Compare
Workflows with 100+ large (100MB+) file outputs lead to failures in the sidecar. These failures appear to be due to transient errors during the upload phase. Large file outputs (anything > 5MB) lead to a MultipartUpload, and flytecopilot attempts to parallelize file uploads. However, it appears the parallelism causes idle connections from a set of completed uploads to interfere with in-progress connections for other uploads. Since the failures are transient, implement a fix where copilot simply initiates a retry (up to 5 max retries) if a transient error is seen during a flytecopilot raw file upload. This fix is consistent with a similar issue seen previously in Flyte storage writes: flyteorg/flyteadmin#325
ddl-rliu
changed the title
ddl-rliu
force-pushed
the
rliu.writeraw-retry
branch
from
May 14, 2026 02:10
ca37329 to
3674473
Compare
As part of the previous fix, flytecopilot simply initiates a retry (up to 5 max retries) if a transient error is seen during a flytecopilot raw file upload. This corresponds to the following list of four specific transient network errors: - "http: server closed idle connection" - "use of closed network connection" - "EOF" - "write: broken pipe" These four network errors were discovered during the local reproduction of the issue. However, during a live run, a new transient network error "WebidentityErr: failed to retrieve credentials ... status code: 408" was observed (Note the status code 408 in particular). In order to update the retry logic to be more robust against unanticipated transient errors, we relax the retry logic to retry on all errors.
ddl-rliu
force-pushed
the
rliu.writeraw-retry
branch
from
May 14, 2026 22:30
768c882 to
6fd96ae
Compare
3 tasks
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7368 +/- ##
==========================================
- Coverage 58.47% 56.98% -1.50%
==========================================
Files 940 932 -8
Lines 71562 58317 -13245
==========================================
- Hits 41849 33230 -8619
+ Misses 26532 22027 -4505
+ Partials 3181 3060 -121
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Tracking issue
Similar issue to flyteorg/flyteadmin#325
Why are the changes needed?
What changes were proposed in this pull request?
How was this patch tested?
Labels
Please add one or more of the following labels to categorize your PR:
This is important to improve the readability of release notes.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Stack
If you do use
git townto manage PR Stacks, the stack relevant to this PRwill show below. Otherwise, you can ignore this section.
Docs link