-
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
branch-3.0: [opt](load) Add config to control commit lock scope for tables #46996 #47039
Open
liaoxin01
wants to merge
1
commit into
apache:branch-3.0
Choose a base branch
from
liaoxin01:pick_46996_to_origin_branch-3.0
base: branch-3.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
branch-3.0: [opt](load) Add config to control commit lock scope for tables #46996 #47039
liaoxin01
wants to merge
1
commit into
apache:branch-3.0
from
liaoxin01:pick_46996_to_origin_branch-3.0
+31
−13
Conversation
This file contains 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
run buildall |
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
…e#46996) Problem Summary: Previously, all tables required commit locks during transaction commit, which helped reduce conflicts at the MetaService level. However, this approach may not be optimal for all scenarios since only MOW (Merge-on-Write) tables truly need strict concurrency control. This PR adds a new config `enable_commit_lock_for_all_tables` (default: true) to control the commit lock strategy: - When enabled (default): All tables will acquire commit locks during transaction commit, which helps reduce conflicts at MetaService level by queueing transactions at FE level - When disabled: Only MOW tables will acquire commit locks, which may improve concurrency for non-MOW tables but could increase conflicts at MetaService level The default setting maintains the original behavior to avoid potential performance impact from increased MetaService conflicts, while providing flexibility to optimize for different deployment scenarios.
liaoxin01
force-pushed
the
pick_46996_to_origin_branch-3.0
branch
from
January 15, 2025 14:22
866f590
to
fbb5045
Compare
run buildall |
TPC-H: Total hot run time: 41686 ms
|
TPC-DS: Total hot run time: 192794 ms
|
ClickBench: Total hot run time: 32.56 s
|
Sign up for free
to 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.
cherry pick from #46996