domain: make the transaction from initStatsCtx blocking gc

[you06]

What problem does this PR solve?

Issue Number: close #53592

Problem Summary:

The initStatsCtx is not get from internal session pool, so it's not tracked by min start ts service, thus gc lifetime can overtake it easily.

What changed and how does it work?

Insert it into tracked session table and it will block gc.

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.

I reproduce the test mentioned in issue, the stats are loaded successfully after 30min.

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.

fix a bug that tidb will report gc lifetime too short when tidb bootstrap with slow loading statistics

[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 @you06. 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

All modified and coverable lines are covered by tests ✅

Project coverage is 74.8736%. Comparing base (f5ac93e) to head (7e3635b).
Report is 57 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53602        +/-   ##
================================================
+ Coverage   72.6008%   74.8736%   +2.2728%     
================================================
  Files          1505       1507         +2     
  Lines        429827     439654      +9827     
================================================
+ Hits         312058     329185     +17127     
+ Misses        98576      90253      -8323     
- Partials      19193      20216      +1023     

Flag	Coverage Δ
integration	49.1564% <75.0000%> (?)
unit	71.4233% <100.0000%> (-1.1694%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	50.4606% <ø> (+9.0600%)	⬆️

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-28 04:31:38.661307421 +0000 UTC m=+2750852.418442992: ☑️ agreed by hawkingrei.
• 2024-05-28 06:10:28.991745599 +0000 UTC m=+2756782.748881167: ☑️ agreed by qw4990.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, lance6716, qw4990

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:

• OWNERS [hawkingrei,lance6716,qw4990]
• pkg/domain/OWNERS [lance6716]
• pkg/statistics/OWNERS [hawkingrei,qw4990]

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

[you06]

/retest-required

[tiprow]

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

In response to this:

/retest-required

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.

[you06]

/retest

[tiprow]

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

In response to this:

/retest

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.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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