-
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
[chore](conf) Set enable_advance_next_id=true by default #44790
[chore](conf) Set enable_advance_next_id=true by default #44790
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
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
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. |
PR approved by anyone and no changes requested. |
run feut |
1a5eaf1
to
83249b0
Compare
run buildall |
TPC-H: Total hot run time: 32466 ms
|
TPC-DS: Total hot run time: 190868 ms
|
ClickBench: Total hot run time: 31.12 s
|
b1471f5
run buildall |
TPC-H: Total hot run time: 32515 ms
|
TPC-DS: Total hot run time: 191130 ms
|
ClickBench: Total hot run time: 32.02 s
|
run feut |
run buildall |
TPC-H: Total hot run time: 32474 ms
|
TPC-DS: Total hot run time: 189872 ms
|
ClickBench: Total hot run time: 31.58 s
|
run buildall |
run buildall |
TPC-H: Total hot run time: 32733 ms
|
TPC-DS: Total hot run time: 190741 ms
|
ClickBench: Total hot run time: 31.5 s
|
PR approved by at least one committer and no changes requested. |
Bind the generation of next_id to physical time to ensure its generation is monotonically increasing, even if we directly overwrite the FE metadata and then restart. This way, it supports a lossy cluster rollback in scenarios where major version upgrades are incompatible.
Bind the generation of next_id to physical time to ensure its generation is monotonically increasing, even if we directly overwrite the FE metadata and then restart. This way, it supports a lossy cluster rollback in scenarios where major version upgrades are incompatible.
What problem does this PR solve?
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)