br: concurrently repairing indexes

[Leavrth]

What problem does this PR solve?

Issue Number: close #59158

Problem Summary:
Currently BR repairs ingest indexes (delete + add index) one by one, which can not take advantage of the DDL concurrent adding indexes feature.

What changed and how does it work?

Create more sessions to repair ingest indexes concurrently.

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-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 54.16667% with 44 lines in your changes missing coverage. Please review.

Project coverage is 74.7315%. Comparing base (9c37399) to head (c54028b).
Report is 118 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59159        +/-   ##
================================================
+ Coverage   73.0489%   74.7315%   +1.6826%     
================================================
  Files          1684       1706        +22     
  Lines        466386     484027     +17641     
================================================
+ Hits         340690     361721     +21031     
+ Misses       104751     100013      -4738     
- Partials      20945      22293      +1348     

Flag	Coverage Δ
integration	46.1407% <47.9166%> (?)
unit	72.4080% <52.0833%> (+0.1662%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	60.0599% <54.1666%> (+14.7367%)	⬆️

[3pointer]

...Actually this is safe if you only use these sessions in the function and not share them

[3pointer]

rest LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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,BornChanger]

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:

• 2025-02-06 06:18:30.77736991 +0000 UTC m=+338982.309781906: ☑️ agreed by BornChanger.
• 2025-02-11 06:31:52.047812447 +0000 UTC m=+338154.444034507: ☑️ agreed by 3pointer.

[Leavrth]

/hold

[Leavrth]

/unhold

[Leavrth]

/ok-to-test

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #59639.
But this PR has conflicts, please resolve them!