domain,server,session: optimize gc safepoint advancing for internal transaction

[TonsnakeLin]

Signed-off-by: TonsnakeLin lpbgytong@163.com

What problem does this PR solve?

TiDB advances gc safepoint every tidb_gc_run_interval time with step tidb_gc_life_time. If there is a long time transaction from user client lives more than tidb_gc_life_time, the safpoint can't be advanced until the long transaction is finished or lives than 24h. This mechanism ensures the continuous advancement of gc safepoint and ensures that the data that active transactions need to access will not be cleared.
However, Internal transactions run in TiDB don't comply with the mechanism above. If the internal transaction lives more than tidb_gc_life_time, maybe failed because the data it needs to access was cleared. This PR is used to solve the problem that internal transactions run in TiDB may be executed failed because the accessed data was cleared.

Issue Number: close #32725

Problem Summary:

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• sticnarf
• youjiali1995

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/4064ae46eaccec40859cb753bf73d79079dcc36e

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[TonsnakeLin]

/run-check_title

[TonsnakeLin]

/run-check_dev

[TonsnakeLin]

@cfzjywxk @MyonKeminta @youjiali1995 @sticnarf @you06 ,thanks !!

[TonsnakeLin]

@cfzjywxk @MyonKeminta @youjiali1995 @sticnarf @you06

[sticnarf]

LGTM

[youjiali1995]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 539fe82

[cfzjywxk]

/merge

[cfzjywxk]

/run-unit-test

[ti-chi-bot]

@TonsnakeLin: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.