[optimize](sink) Optimize the BE load balancing logic during concurrent imports. #388
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
vinlee19
changed the title
JNSimba
reviewed
May 17, 2024
flink-doris-connector/src/main/java/org/apache/doris/flink/sink/BackendUtil.java
Outdated
Show resolved
Hide resolved
PeatBoy
pushed a commit
to hyperpaas/doris-flink-connector
that referenced
this pull request
Jan 21, 2025
…nt imports. (apache#388) (cherry picked from commit d9f52e6)
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.
Proposed changes
For example, consider multiple BEs in Apache Doris. The load is not balanced during concurrent imports. At the same checkpoint, multiple stream load tasks are directed to the same BE, causing server pressure on the backends because the
Posvariables are the same within the checkpoint. To address this, we can calculate the destination BE using both thesubTaskIdandPosvariables.Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...