br: Release 8.5 20250114 v8.5.0

[YuJuncen]

What problem does this PR solve?

Issue Number: N/A

Problem Summary:
This hotfix includes patches needed by the compatibility between log backup and restore snapshot.

What changed and how does it work?

The following PRs are picked:

• br/operator: added some commands for managing migrations #56857 1de6f3e
• Restore: refine split code for both compacted sst files and logs #56917 ef6662e
• br: implement reading migration #57237 169210a
• Restore: implement restorer for compacted SST/Snapshot/log files #57208 9530fdc
• external_storage: implement locking #56597 ea7ec59
• test: fix the data race in restore test #57762 0471081
• br/stream: added --delete-compactions to log truncate #56761 65e233e
• BR: support restore compacted logs with checkpoint #57532 b5b8109
• compacted restore: fix the wrong initial configrations #58050 b416484
• compact restore: use closure to initial snapshot restore checkpoint #58146 659e3e7
• br/cmd: added operator checksum-as|force-flush #58801 0c6681f
• br: copy full backup to pitr storage #57716 c9215ec

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 @YuJuncen. 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 39.13548% with 2098 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.5-20250114-v8.5.0@ad2e1cd). Learn more about missing BASE report.

Additional details and impacted files

@@                       Coverage Diff                        @@
##             release-8.5-20250114-v8.5.0     #58981   +/-   ##
================================================================
  Coverage                               ?   23.8338%           
================================================================
  Files                                  ?       1683           
  Lines                                  ?     610639           
  Branches                               ?          0           
================================================================
  Hits                                   ?     145539           
  Misses                                 ?     446671           
  Partials                               ?      18429           

Flag	Coverage Δ
integration	23.8338% <39.1354%> (?)

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

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-01-16 08:01:55.125226184 +0000 UTC m=+191986.580272344: ☑️ agreed by BornChanger.
• 2025-01-16 08:17:53.083310257 +0000 UTC m=+192944.538356401: ☑️ agreed by D3Hunter.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from yujuncen and additionally assign d3hunter for approval(Please ensuring that each of them provides their approval before proceeding). For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS
• br/OWNERS
• br/pkg/storage/OWNERS
• pkg/lightning/OWNERS

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]

@YuJuncen: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/unit-test	f342b7c	link	true	/test unit-test
idc-jenkins-ci-tidb/build	f342b7c	link	true	/test build
idc-jenkins-ci-tidb/check_dev	f342b7c	link	true	/test check-dev

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.