-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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](recycler) Fix potential data leak when a partial update load which has publish conflict fails #45626
[Fix](recycler) Fix potential data leak when a partial update load which has publish conflict fails #45626
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
clang-tidy review says "All clean, LGTM! 👍" |
e3921f6
to
d6a9619
Compare
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.
clang-tidy made some suggestions
clang-tidy review says "All clean, LGTM! 👍" |
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
d6a9619
to
471c591
Compare
run buildall |
c0c9f71
to
4b8815e
Compare
4b8815e
to
cac72db
Compare
run buildall |
PR approved by at least one committer and no changes requested. |
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
…ich has publish conflict fails (apache#45626) ### What problem does this PR solve? when recycling tmp rowsets, if rowset's state is `RowsetStatePB::BEGIN_PARTIAL_UPDATE`, the `num_segments` field in `RowsetMetaCloudPB` may not reflect the actual segments num(This may happen if partial update load writes a new segment to an existing tmp rowset in publish phase due to conflict and fails before it updates segments num in `RowsetMetaCloudPB` in MS successfully). So we need to delete the rowsets by prefix rather than delete by path in this case. related case: apache#45795
What problem does this PR solve?
when recycling tmp rowsets, if rowset's state is
RowsetStatePB::BEGIN_PARTIAL_UPDATE
, thenum_segments
field inRowsetMetaCloudPB
may not reflect the actual segments num(This may happen if partial update load writes a new segment to an existing tmp rowset in publish phase due to conflict and fails before it updates segments num inRowsetMetaCloudPB
in MS successfully). So we need to delete the rowsets by prefix rather than delete by path in this case.related case: #45795
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)