br: stop log when full restore failed

[Leavrth]

What problem does this PR solve?

Issue Number: close #51572

Problem Summary:
too many logs when full restore failed

What changed and how does it work?

stop log when error context canceled

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.

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 @Leavrth. 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/test-infra repository.

[codecov]

Codecov Report

Merging #51578 (42ebaff) into master (7b6fc23) will increase coverage by 2.0156%.
Report is 42 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51578        +/-   ##
================================================
+ Coverage   70.7753%   72.7909%   +2.0156%     
================================================
  Files          1464       1473         +9     
  Lines        436300     444665      +8365     
================================================
+ Hits         308793     323676     +14883     
+ Misses       108167     100691      -7476     
- Partials      19340      20298       +958     

Flag	Coverage Δ
integration	48.7865% <54.5454%> (?)
unit	70.4518% <45.4545%> (-0.1216%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.2004% <100.0000%> (+5.3243%)	⬆️

[Leavrth]

pdclient := mgr.GetPDClient()
cctx, cancel := context.WithCancel(ctx)
cancel()
_, _, err = pdclient.GetTS(cctx)
require.Equal(t, context.Canceled, errors.Cause(err))  // pass 
require.NoError(t, err)  // Received unexpected error:
        	         //   context canceled

It is not grpc context cancel error, so we can retry the grpc context cancel error in pd backoff

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, 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 [3pointer,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]

[LGTM Timeline notifier]

Timeline:

• 2024-03-11 06:01:03.578685058 +0000 UTC m=+665290.600931447: ☑️ agreed by 3pointer.
• 2024-03-11 06:49:19.098354254 +0000 UTC m=+668186.120600637: ☑️ agreed by YuJuncen.

[Leavrth]

/ok-to-test

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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