-
Notifications
You must be signed in to change notification settings - Fork 3.7k
branch-3.0-pick: [Fix](cloud-mow) Fix race between CloudMetaMgr::sync_tablet_rowsets and CloudSchemaChangeJob::_convert_historical_rowsets (#50051)
#50081
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
… and `CloudSchemaChangeJob::_convert_historical_rowsets` (apache#50051) Considering the following race situation: 1. thread 1 finish convert historical rowsets before version Y on tablet A and write tmp converted rowset metas on MS 2. thread 2 begins sync_rowsets on tablet A with version Y and get visible rowsets before version Y. 3. thread 1 commit heavy schema change job on MS and turn tmp converted historical rowsets to visible rowsets on tablet Y. 4. thread 1 add converted historical rowset metas to tablet Y's BE local tablet meta and remove all delete bitmaps of new tablet before version Y. 5. thread 2 **add rowsets to tablet Y's BE local tablet meta which overwrites schema change's converted rowsets**. This will cause correctness problem. This PR add a lock to avoid this situation.
6ea3266 to
76cec48
Compare
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 40369 ms |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-DS: Total hot run time: 197961 ms |
ClickBench: Total hot run time: 31.96 s |
Contributor
Author
|
run p0 |
dataroaring
approved these changes
Apr 22, 2025
Contributor
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
pick #50051