br: fix insert gc failed due to slow schema reload

[Tristan1900]

What problem does this PR solve?

Issue Number: close #57743

Problem Summary:

What changed and how does it work?

Wait until schema info finished reloading before proceeding to the rest of the restore process,
Added test to first to reproduce the issue and then add the fix to verify the issue has been fixed (TDD)

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.

Fixed loading schema taking long time during restore causing insertGc row and other operations to fail  

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @Tristan1900. 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.

[Tristan1900]

/ok-to-test

[codecov]

Codecov Report

Attention: Patch coverage is 43.33333% with 34 lines in your changes missing coverage. Please review.

Project coverage is 75.3716%. Comparing base (2b03447) to head (b9d541a).
Report is 128 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57742        +/-   ##
================================================
+ Coverage   72.8732%   75.3716%   +2.4984%     
================================================
  Files          1677       1731        +54     
  Lines        464202     481515     +17313     
================================================
+ Hits         338279     362926     +24647     
+ Misses       105016      96406      -8610     
- Partials      20907      22183      +1276     

Flag	Coverage Δ
integration	49.8512% <41.6666%> (?)
unit	72.8531% <1.6666%> (+0.5827%)	⬆️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	61.5786% <55.5555%> (+15.8750%)	⬆️

[Tristan1900]

/assign @Leavrth

[Tristan1900]

/assign @lance6716

[3pointer]

rest LGTM

[3pointer]

how about put waitUntilSchemaReload after CleanUpKVFiles?

[lance6716]

domain part lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, lance6716, Leavrth

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,Leavrth]
• pkg/domain/OWNERS [lance6716]

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

[lance6716]

/check-issue-triage-complete

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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