[feat](cloud) Support cloud group commit stream load BE forward mode#55326
Merged
dataroaring merged 1 commit intoapache:masterfrom Aug 29, 2025
Merged
[feat](cloud) Support cloud group commit stream load BE forward mode#55326dataroaring merged 1 commit intoapache:masterfrom
dataroaring merged 1 commit intoapache:masterfrom
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.
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
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 |
Contributor
FE UT Coverage ReportIncrement line coverage |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
gavinchou
approved these changes
Aug 29, 2025
Closed
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 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.
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)