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

don't trigger retry for s3 ec2metadata when error is connection reset by peer #47650

Closed
Leavrth opened this issue Oct 16, 2023 · 0 comments · Fixed by #47651
Closed

don't trigger retry for s3 ec2metadata when error is connection reset by peer #47650

Leavrth opened this issue Oct 16, 2023 · 0 comments · Fixed by #47651
Labels
affects-6.5 affects-7.1 affects-7.5 component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@Leavrth
Copy link
Contributor

Leavrth commented Oct 16, 2023

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. log restore in the s3 environment

2. What did you expect to see? (Required)

"failed to get EC2 metadata. skipping."
context deadline exceed

3. What did you see instead (Required)

"failed to request s3. retrying"
connection reset by peer

4. What is your TiDB version? (Required)

master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 affects-7.1 affects-7.5 component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant