Uh oh!
There was an error while loading. Please reload this page.
[chore](conf) Set enable_advance_next_id=true by default - #44790
Merged
Conversation
doris-robot
commented
Nov 29, 2024
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
gavinchou
commented
Nov 29, 2024
ContributorAuthor
run buildall |
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
gavinchou
commented
Dec 31, 2024
ContributorAuthor
run feut |
gavinchouforce-pushed
the
gavin-advance-id-by-default
branch
from
December 31, 2024 09:12
1a5eaf1 to
83249b0Comparegavinchou
commented
Dec 31, 2024
ContributorAuthor
run buildall |
doris-robot
commented
Dec 31, 2024
TPC-H: Total hot run time: 32466 ms |
doris-robot
commented
Dec 31, 2024
TPC-DS: Total hot run time: 190868 ms |
doris-robot
commented
Dec 31, 2024
ClickBench: Total hot run time: 31.12 s |
gavinchou
dismissed stale reviews from zhannngchen and dataroaring
via
December 31, 2024 11:59
b1471f5gavinchou
commented
Dec 31, 2024
ContributorAuthor
run buildall |
doris-robot
commented
Dec 31, 2024
TPC-H: Total hot run time: 32515 ms |
doris-robot
commented
Dec 31, 2024
TPC-DS: Total hot run time: 191130 ms |
doris-robot
commented
Dec 31, 2024
ClickBench: Total hot run time: 32.02 s |
gavinchou
commented
Jan 1, 2025
ContributorAuthor
run feut |
gavinchou
commented
Jan 1, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 1, 2025
TPC-H: Total hot run time: 32474 ms |
doris-robot
commented
Jan 1, 2025
TPC-DS: Total hot run time: 189872 ms |
doris-robot
commented
Jan 1, 2025
ClickBench: Total hot run time: 31.58 s |
gavinchou
commented
Jan 2, 2025
ContributorAuthor
run buildall |
gavinchou
commented
Jan 3, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 3, 2025
TPC-H: Total hot run time: 32733 ms |
doris-robot
commented
Jan 3, 2025
TPC-DS: Total hot run time: 190741 ms |
doris-robot
commented
Jan 3, 2025
ClickBench: Total hot run time: 31.5 s |
bobhan1
approved these changes
Jan 3, 2025
liaoxin01
approved these changes
Jan 3, 2025
Contributor
PR approved by at least one committer and no changes requested. |
zhannngchen
approved these changes
Jan 3, 2025
gavinchou added a commit
to gavinchou/doris
that referenced
this pull request
Jan 5, 2025
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.
16 tasks
Closed
hubgeter pushed a commit
to hubgeter/doris
that referenced
this pull request
Mar 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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)