-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[fix][mow] segment_creator should not flush data when encouter abnormal exit #33802
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
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
BaseBetaRowsetWriter::~BaseBetaRowsetWriter() { | ||
// TODO(lingbin): Should wrapper exception logic, no need to know file ops directly. | ||
if (!_already_built) { // abnormal exit, remove all files generated | ||
WARN_IF_ERROR(_segment_creator.close(), |
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.
we may need to check if the state of this writer.
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. |
TPC-H: Total hot run time: 38711 ms
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 184973 ms
|
ClickBench: Total hot run time: 30.55 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
when encouter abnormal exit, the data maybe inconsistent in primary_key_index, and no need to flush data, so should not call close in here.
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...