PageStorage: Optimize the critical region when removing a BlobFile from disk (#8651) #8654
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.
This is an automated cherry-pick of #8651
What problem does this PR solve?
Issue Number: close #8650
Problem Summary:
When all page data in a BlobFile gets removed in the GC thread,
removePosFromStats
will remove the BlobFile from disk. However, it holds a lock onmtx_blob_files
when removing the file from disk. IfBlobStore::write
happens to write a page data to a new BlobFile,BlobStore::getBlobFile
will be blocked by the GC thread.According to local tests, removing a BlobFile takes tens of milliseconds. Thus introducing performance jitter.
tiflash/dbms/src/Storages/Page/V3/BlobStore.cpp
Lines 803 to 814 in 63eb295
tiflash/dbms/src/Storages/Page/V3/BlobStore.cpp
Lines 632 to 636 in 63eb295
tiflash/dbms/src/Storages/Page/V3/BlobStore.cpp
Lines 1494 to 1503 in 63eb295
What is changed and how it works?
Keep a pointer within the lock on
mtx_blob_files
, and remove the blob file from disk without the lockCheck List
Tests
Side effects
Documentation
Release note