Uh oh!
There was an error while loading. Please reload this page.
[improve](routine load) ensure load balance after scaling up BE nodes - #44693
Merged
Conversation
doris-robot
commented
Nov 27, 2024
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
sollhui
commented
Nov 27, 2024
ContributorAuthor
run buildall |
doris-robot
commented
Nov 27, 2024
TPC-H: Total hot run time: 39952 ms |
doris-robot
commented
Nov 27, 2024
TPC-DS: Total hot run time: 197091 ms |
doris-robot
commented
Nov 27, 2024
ClickBench: Total hot run time: 32.56 s |
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
sollhuiforce-pushed
the
rl_load_balance
branch
from
November 28, 2024 08:27
00d950a to
c6bac64Comparesollhui
commented
Nov 28, 2024
ContributorAuthor
run buildall |
doris-robot
commented
Nov 28, 2024
TPC-H: Total hot run time: 40193 ms |
doris-robot
commented
Nov 28, 2024
TPC-DS: Total hot run time: 191732 ms |
doris-robot
commented
Nov 28, 2024
ClickBench: Total hot run time: 31.76 s |
Contributor
PR approved by at least one committer and no changes requested. |
github-actionsBot
pushed a commit
that referenced
this pull request
Nov 29, 2024
…#44693) We scaling up from three BE nodes to five BE nodes, but from the monitoring perspective, only the previous three nodes have written traffic.  This pr aims to ensure load balance after scaling up BE nodes.
github-actionsBot
pushed a commit
that referenced
this pull request
Nov 29, 2024
…#44693) We scaling up from three BE nodes to five BE nodes, but from the monitoring perspective, only the previous three nodes have written traffic.  This pr aims to ensure load balance after scaling up BE nodes.
HappenLee pushed a commit
to HappenLee/incubator-doris
that referenced
this pull request
Apr 24, 2026
…apache#44693) We scaling up from three BE nodes to five BE nodes, but from the monitoring perspective, only the previous three nodes have written traffic.  This pr aims to ensure load balance after scaling up BE nodes.
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.
What problem does this PR solve?
We scaling up from three BE nodes to five BE nodes, but from the monitoring perspective, only the previous three nodes have written traffic.

This pr aims to ensure load balance after scaling up BE nodes.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)