Check stale file information and remove Rename operation in encryption module

[hunterlxt]

Signed-off-by: Xintao hunterlxt@live.com

cherry-pick #9285 to release-4.0

What problem does this PR solve?

Issue Number: close #9115

Problem Summary:

This PR is to solve the stale information encountered in the encryption dictionary

• Delete: When deleting a file but failing to execute delete_file on file_dict, the stale information leaves
• Rename: When a new dst_fname is added to the dictionary file, but the real rename is not successful or execute rename but failed to delete src_fname
• Link: When a new dst_fname is added to the dictionary file, the subsequent operations don't finish.

In the above situation, some stale file information will appear in the encrypted file dictionary. We need to deal with these errors instead of generating and returning errors.

What is changed and how it works?

Proposal: xxx

What's Changed:

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tidb-ansible:
• Need to cherry-pick to the release branch

Check List

Tests

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

Side effects

• Performance regression
  • Consumes more CPU
  • Consumes more MEM
• Breaking backward compatibility

Release note

Check stale file information from encryption file dict

[hunterlxt]

/run-all-tests

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hicqu
• yiwu-arbug

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.

[BusyJay]

/merge

[ti-chi-bot]

@BusyJay: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and 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.

If you have any questions about the PR merge process, please refer to pr process.

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.

[ti-chi-bot]

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

Commit hash: 413a782

[ti-chi-bot]

@hunterlxt: 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.