Check stale file information and remove Rename operation in encryption module #10598
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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_file
onfile_dict
, the stale information leavesdst_fname
is added to the dictionary file, but the realrename
is not successful or executerename
but failed to deletesrc_fname
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
pingcap/docs
/pingcap/docs-cn
:pingcap/tidb-ansible
:Check List
Tests
Side effects
Release note