Skip to content

url: increase S3 and TFTP retries#468

Closed
lucab wants to merge 3 commits intocoreos:masterfrom
lucab:ups/urls-retries
Closed

url: increase S3 and TFTP retries#468
lucab wants to merge 3 commits intocoreos:masterfrom
lucab:ups/urls-retries

Conversation

@lucab
Copy link
Contributor

@lucab lucab commented Oct 9, 2017

This increases the number of retries performed by the TFTP and S3 clients in case of transient network errors.

Fixes OST-73

Copy link
Contributor

@cgonyeo cgonyeo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Since the HTTP retry logic is described in the operator's notes, maybe it would be worth adding a sentence or two there on the fact that S3 and TFTP will now retry failed attempts.

@lucab
Copy link
Contributor Author

lucab commented Oct 9, 2017

Ack, thanks for pointing out the docs. I will drop a note there.

maxRetries := int(10)
f.AWSSession, err = session.NewSession(&aws.Config{
Credentials: credentials.AnonymousCredentials,
MaxRetries: &maxRetries,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is slightly more readable as aws.Int(10) if we're hardcoding it anyways.

For reference, this is bumping from the default of 3.

With or without my slight readability nit, this LGTM.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am curios how the number 10 was picked though; if you have any information leading to that being a better number than 3 or 5, I'd be interested in hearing it.

I assume the SDK's value was chosen for a reason (especially given all the sdks share 3 for s3, use 10 for certain dynamodb requests, etc etc)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bad answer: it's an arbitrary number bumping over the initial default (both for S3 and TFTP). Actual number was a hint from the initial ticket, but that was arbitrary as well. Both clients already do retries so this PR just ups, uniforms and makes the number explicit.

@robszumski
Copy link
Member

Bump on this. Good to go?

@arithx
Copy link
Contributor

arithx commented Oct 20, 2017

Needs to be rebased

lucab added 3 commits October 26, 2017 10:04
This increases the number of retries performed by the TFTP client
in case of transient network errors.
This increases the number of retries performed by the S3 client
in case of transient network errors.
This adds a quick operator-note concerning retries of TFTP and S3
downloads.
@crawford
Copy link
Contributor

The original bug was speculative, disproved, and ultimately closed out, so I don't think we need this patch.

@crawford crawford closed this Nov 20, 2017
prestist added a commit to prestist/ignition that referenced this pull request Jan 12, 2026
…b.com/stretchr/testify-1.8.3

build(deps): bump github.com/stretchr/testify from 1.8.2 to 1.8.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants