-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[feat](cloud) Support cloud group commit stream load BE forward mode #55326
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
…de (apache#4113) Handle stream load redirect with optional group commit forwarding. Group Commit Stream Load Forward Mode in Cloud Environment: Problem: Group commit requires that requests for the same table be sent to the same BE node to achieve better batching efficiency. However, in cloud mode with Load Balancer (LB), the LB randomly selects a BE node for forwarding, which breaks the group commit strategy and reduces batching effectiveness. Solution: Implement a two-stage forwarding mechanism: 1. FE redirects to public/private endpoint (LB) as usual 2. BE performs a second forwarding to the actual target BE node that handles the specific table This ensures that all requests for the same table ultimately reach the same BE node, preserving the group commit batching strategy while still utilizing the LB infrastructure.
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 33516 ms |
TPC-DS: Total hot run time: 182174 ms |
ClickBench: Total hot run time: 32.1 s |
FE UT Coverage ReportIncrement line coverage |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
…orward mode #55326 (#55527) Cherry-picked from #55326 Co-authored-by: Xin Liao <[email protected]>
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Group Commit Stream Load Forward Mode in Cloud Environment:
Problem:
Group commit requires that requests for the same table be sent to the same BE node
to achieve better batching efficiency. However, in cloud mode with Load Balancer (LB),
the LB randomly selects a BE node for forwarding, which breaks the group commit strategy
and reduces batching effectiveness.
Solution:
Implement a two-stage forwarding mechanism:
This ensures that all requests for the same table ultimately reach the same BE node,
preserving the group commit batching strategy while still utilizing the LB infrastructure.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)