Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actually record last retry time after reconnecting #2608

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

mtrmac
Copy link
Collaborator

@mtrmac mtrmac commented Oct 21, 2024

The code was incorrectly setting it to "never", meaning the bodyReaderMSSinceLastRetry heuristic was never triggered, and, in effect, we would always reconnect on io.ErrUnexpectedEOF or syscall.ECONNRESET .

This corrects the code - but it might also make more network failures user-visible instead of silently retried.

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

LGTM

@rhatdan
Copy link
Member

rhatdan commented Oct 22, 2024

LGTM

@mtrmac mtrmac force-pushed the retries-time branch 2 times, most recently from 6516e7e to 4ebce02 Compare October 24, 2024 13:04
@cgwalters
Copy link
Contributor

/lgtm

The code was incorrectly setting it to "never", meaning the
bodyReaderMSSinceLastRetry heuristic was never triggered,
and, in effect, we would _always_ reconnect on io.ErrUnexpectedEOF
or syscall.ECONNRESET .

This corrects the code - but it might also make more network failures
user-visible instead of silently retried.

Signed-off-by: Miloslav Trmač <[email protected]>
@mtrmac mtrmac merged commit e07ae87 into containers:main Oct 25, 2024
10 checks passed
@mtrmac mtrmac deleted the retries-time branch October 25, 2024 20:38
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.

4 participants