compacted restore: fix the wrong initial configrations

[3pointer]

What problem does this PR solve?

Issue Number: ref #56522
Problem Summary:

1. the initial config concurrencyPerStore of snapclient is not right. which make the compacted restore blocked. This PR try to fix it.
2. the initial checkpoint for compacted restore is not complete. this PR fix it.

What changed and how does it work?

set the correct config. and add a config check when initialize

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 @3pointer. 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.

[3pointer]

/hold for manual test result

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

[LGTM Timeline notifier]

Timeline:

• 2024-12-06 07:14:25.877470061 +0000 UTC m=+1398253.497124572: ☑️ agreed by YuJuncen.
• 2024-12-06 07:36:18.008884864 +0000 UTC m=+1399565.628539377: ☑️ agreed by Leavrth.

[codecov]

Codecov Report

Attention: Patch coverage is 54.54545% with 15 lines in your changes missing coverage. Please review.

Project coverage is 75.2532%. Comparing base (bb9096c) to head (85e0978).
Report is 12 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58050        +/-   ##
================================================
+ Coverage   73.1711%   75.2532%   +2.0820%     
================================================
  Files          1674       1720        +46     
  Lines        461507     473654     +12147     
================================================
+ Hits         337690     356440     +18750     
+ Misses       103079      95053      -8026     
- Partials      20738      22161      +1423     

Flag	Coverage Δ
integration	49.2431% <45.4545%> (?)
unit	72.5003% <18.1818%> (+0.2032%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	61.7627% <54.5454%> (+15.7794%)	⬆️

[3pointer]

/test pull-br-integration-test

[tiprow]

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

In response to this:

/test pull-br-integration-test

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.

[3pointer]

/ok-to-test

[3pointer]

/unhold

[3pointer]

/test pull-br-integration-test

[tiprow]

@3pointer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test fast_test_tiprow_ddlargsv1
• /test tidb_parser_test

Use /test all to run the following jobs that were automatically triggered:

• fast_test_tiprow
• tidb_parser_test

In response to this:

/test pull-br-integration-test

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.

[3pointer]

/test mysql-test

[tiprow]

@3pointer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test fast_test_tiprow_ddlargsv1
• /test tidb_parser_test

Use /test all to run the following jobs that were automatically triggered:

• fast_test_tiprow
• tidb_parser_test

In response to this:

/test mysql-test

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.

[3pointer]

/test pull-br-integration-test

[tiprow]

@3pointer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test fast_test_tiprow_ddlargsv1
• /test tidb_parser_test

Use /test all to run the following jobs that were automatically triggered:

• fast_test_tiprow
• tidb_parser_test

In response to this:

/test pull-br-integration-test

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.