*: merge master to feature/active-active

[lcwangchao]

What problem does this PR solve?

Issue Number: ref #64281

Problem Summary:

What changed and how does it work?

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

[lcwangchao]

/retest

[codecov]

Codecov Report

❌ Patch coverage is 77.97588% with 420 lines in your changes missing coverage. Please review.
✅ Project coverage is 79.2959%. Comparing base (54293b0) to head (91c63e0).
⚠️ Report is 2 commits behind head on feature/active-active.

Additional details and impacted files

@@                      Coverage Diff                      @@
##           feature/active-active     #66011        +/-   ##
=============================================================
- Coverage                79.3164%   79.2959%   -0.0205%     
=============================================================
  Files                       1950       1952         +2     
  Lines                     534995     536553      +1558     
=============================================================
+ Hits                      424339     425465      +1126     
- Misses                    109168     109601       +433     
+ Partials                    1488       1487         -1     

Flag	Coverage Δ
integration	48.2263% <45.5393%> (+0.2854%)	⬆️
unit	76.3456% <75.0393%> (-0.0230%)	⬇️

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

Components	Coverage Δ
dumpling	56.7974% <ø> (ø)
parser	∅ <ø> (∅)
br	66.1468% <68.6868%> (-0.2024%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lcwangchao]

/retest

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-02-04 04:30:48.33024472 +0000 UTC m=+241319.431643440: ☑️ agreed by time-and-fate.
• 2026-02-04 04:39:59.554469733 +0000 UTC m=+241870.655868446: ☑️ agreed by xhebox.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: time-and-fate, xhebox
Once this PR has been reviewed and has the lgtm label, please assign 3pointer, benmeadowcroft, cfzjywxk, d3hunter, time-and-fate, zanmato1984 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS [time-and-fate,xhebox]

  Need more approvers for rest parts.

• br/OWNERS
• lightning/OWNERS
• pkg/bindinfo/OWNERS [time-and-fate]
• pkg/ddl/OWNERS
• pkg/domain/OWNERS
• pkg/executor/importer/OWNERS
• pkg/expression/OWNERS
• pkg/lightning/OWNERS
• pkg/meta/OWNERS
• pkg/meta/metadef/OWNERS
• pkg/objstore/OWNERS
• pkg/parser/OWNERS
• pkg/planner/OWNERS [time-and-fate]
• pkg/session/OWNERS
• pkg/sessionctx/vardef/OWNERS
• pkg/sessionctx/variable/OWNERS
• pkg/statistics/OWNERS [time-and-fate]
• pkg/table/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]

@lcwangchao: The following test 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	91c63e0	link	unknown	/test unit-test

Full PR test history. Your PR dashboard.

Details

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.