-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](cooldown) Fix bug in follow cooldowned data #32798
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. |
|
PR approved by anyone and no changes requested. |
|
clang-tidy review says "All clean, LGTM! 👍" |
964125a to
e21228b
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
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
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
|
TeamCity be ut coverage result: |
e21228b to
8757cf6
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 37748 ms |
TPC-DS: Total hot run time: 181761 ms |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
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
Proposed changes
The single replica cooldown protocal in Doris must maintain the invariant that cooldowned rowsets of a replica exactly corresponds to the cooldown meta id, however skipping rowsets with the same version when following cooldowned data would break this invariant. Modifying the code to skip rowsets with the same rowset id can maintain the invariant.
This PR also fix another potential data loss problem.
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...