log-backup: set gc disable when restore log (#39729)

[ti-chi-bot]

This is an automated cherry-pick of #39729

Signed-off-by: joccau zak.zhao@pingcap.com

What problem does this PR solve?

Issue Number: close #39602

Problem Summary:
The restoring data is gc when pitr. because the process of applying kv-events is concurrent and the kv-events is not sorted by tso.

What is changed and how it works?

• Disable gc when pitr by set config tikv gc.ratio-threshold= -1.0

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Manual tesst

1. During PITR

MySQL [(none)]> show config where name = 'gc.ratio-threshold';
+------+-------------------+--------------------+-------+
| Type | Instance          | Name               | Value |
+------+-------------------+--------------------+-------+
| tikv | 172.16.6.47:13460 | gc.ratio-threshold | -1    |
| tikv | 172.16.6.35:3460  | gc.ratio-threshold | -1    |
| tikv | 172.16.6.35:13460 | gc.ratio-threshold | -1    |
| tikv | 172.16.6.46:13460 | gc.ratio-threshold | -1    |
| tikv | 172.16.6.46:3460  | gc.ratio-threshold | -1    |
| tikv | 172.16.6.47:3460  | gc.ratio-threshold | -1    |
+------+-------------------+--------------------+-------+

2. finish PITR

MySQL [(none)]> show config where name = 'gc.ratio-threshold';
+------+-------------------+--------------------+-------+
| Type | Instance          | Name               | Value |
+------+-------------------+--------------------+-------+
| tikv | 172.16.6.47:3460  | gc.ratio-threshold | 1.1   |
| tikv | 172.16.6.47:13460 | gc.ratio-threshold | 1.1   |
| tikv | 172.16.6.35:3460  | gc.ratio-threshold | 1.1   |
| tikv | 172.16.6.35:13460 | gc.ratio-threshold | 1.1   |
| tikv | 172.16.6.46:13460 | gc.ratio-threshold | 1.1   |
| tikv | 172.16.6.46:3460  | gc.ratio-threshold | 1.1   |
+------+-------------------+--------------------+-------+

3. admin check table after PITR finished

MySQL [(none)]> admin check table flashback.user_data1;
Query OK, 0 rows affected (1.61 sec)

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.

Disable GC when restore log(PITR) and Enable GC when finish PITR.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Leavrth
• joccau

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.

[joccau]

LGTM

[joccau]

/merge

[ti-chi-bot]

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

Commit hash: 4263168

[ti-chi-bot]

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

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.