-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Fix](cloud-mow) Remove potential existing split delete bitmap KVs before update them in schema change #51353
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
[Fix](cloud-mow) Remove potential existing split delete bitmap KVs before update them in schema change #51353
Conversation
|
run buildall |
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 33933 ms |
TPC-DS: Total hot run time: 192625 ms |
ClickBench: Total hot run time: 29.64 s |
8ed9703 to
5649633
Compare
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
zhannngchen
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
…fore update them in schema change (apache#51353) If a schema change job failed and retry on BE, the previous failed sc job will not clear its delete bitmap KVs written in MS. So later retry may update existing delete bitmap KVs on new tablet. Considering that delete bitmap KVs will be split into multiple KVs when too large, we may get wrong delete bitmaps if we don't remove the previous KVs before put them. This PR use pending delete bitmaps to avoid this situation for SC.
…itmap KVs before update them in schema change (apache#51353) (apache#51531) pick apache#51353
What problem does this PR solve?
If a schema change job failed and retry on BE, the previous failed sc job will not clear its delete bitmap KVs written in MS. So later retry may update existing delete bitmap KVs on new tablet. Considering that delete bitmap KVs will be split into multiple KVs when too large, we may get wrong delete bitmaps if we don't remove the previous KVs before put them.
This PR use pending delete bitmaps to avoid this situation for SC.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)