br: Add retry limit of connection err in fine grained backup

[RidRisR]

What problem does this PR solve?

Issue Number: close #57449

Problem Summary:

The fine grained backup may fails into infinite retry when encounter disconnect err.

What changed and how does it work?

Add a retry limit of 3 to each store.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Try to make error in resp 3 times, will get:

Error: failed to connect to store 1 for 3 times: failed to connect to store 1: [BR:Common:ErrFailedToConnect]failed to make gRPC channels

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @RidRisR. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 31 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.1@4c32fcc). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.1     #57713   +/-   ##
================================================
  Coverage               ?   71.2293%           
================================================
  Files                  ?       1467           
  Lines                  ?     423473           
  Branches               ?          0           
================================================
  Hits                   ?     301637           
  Misses                 ?     101357           
  Partials               ?      20479           

Flag	Coverage Δ
unit	71.2293% <0.0000%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9656% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	41.3050% <0.0000%> (?)

[purelind]

/retest

[tiprow]

@purelind: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Tristan1900]

LGTM, do we need a test to verify it's working as expected?

[RidRisR]

LGTM, do we need a test to verify it's working as expected?

Unfortunately there is no handy infrastructure for testing fine grained, and it seems not so worthy to build one for a up to deprecate function.

I impl a basic manual test for it.

[RidRisR]

/test unit-test

[tiprow]

@RidRisR: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[RidRisR]

/test check-dev2

[tiprow]

@RidRisR: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test check-dev2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-11-26 09:30:13.564085335 +0000 UTC m=+542401.183739846: ☑️ agreed by YuJuncen.
• 2024-12-05 02:27:55.896761918 +0000 UTC m=+1294663.516416431: ☑️ agreed by Leavrth.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, Leavrth, YuJuncen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• br/OWNERS [BornChanger,Leavrth,YuJuncen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #58216.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #58347.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #58348.