Skip to content

azblob need retry when connection error occurs #39649

@Leavrth

Description

@Leavrth

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

run br to restore

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

success

3. What did you see instead (Required)

[INFO] [collector.go:69] ["restore log failed summary"] [error="scanning metadata meets error Failed to list azure blobs, bucket(container)='backup-data': context canceled: during reading meta file v1/backupmeta/437743859352207656-bef2cb55-5563-4a18-b00e-208d442763a2.meta from storage: Failed to read azure blob file, file info: bucket(container)='backup-data', key='log-adhoc/v1/backupmeta/437743859352207656-bef2cb55-5563-4a18-b00e-208d442763a2.meta': read tcp [172.*.*.*:*](http://172.*.*.*:*/)->[20.*.*.*:443](http://20.*.*.*:443/): read: connection reset by peer"]

4. What is your TiDB version? (Required)

Metadata

Metadata

Assignees

No one assigned

    Labels

    affects-6.5This bug affects the 6.5.x(LTS) versions.component/brThis issue is related to BR of TiDB.severity/majortype/bugThe issue is confirmed as a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions