Skip to content

branch-4.0: [enhance](job) support adaptive batch param for routine load job#58846

Merged
yiguolei merged 2 commits intoapache:branch-4.0from
sollhui:pick_f34b8c1
Dec 17, 2025
Merged

branch-4.0: [enhance](job) support adaptive batch param for routine load job#58846
yiguolei merged 2 commits intoapache:branch-4.0from
sollhui:pick_f34b8c1

Conversation

@sollhui
Copy link
Contributor

@sollhui sollhui commented Dec 9, 2025

What problem does this PR solve?

pick #56930 and #57967

Users may set the max batch interval relatively small for visibility, which may result in insufficient throughput and data backlog when traffic is high. We propose an adaptive max batch interval scheme aimed at prioritizing throughput over visibility during data backlog

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

…che#56930)

### What problem does this PR solve?

Users may set the `max batch interval` relatively small for visibility,
which may result in insufficient throughput and data backlog when
traffic is high. We propose an adaptive max batch interval scheme aimed
at **prioritizing throughput over visibility during data backlog**
…ptive timeout (apache#57967)

Fix transaction timeout do not match routine load task adaptive timeout,
introduced by apache#56930
@sollhui sollhui requested a review from yiguolei as a code owner December 9, 2025 07:57
@sollhui
Copy link
Contributor Author

sollhui commented Dec 9, 2025

run buildall

@Thearas
Copy link
Contributor

Thearas commented Dec 9, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage 0.00% (0/22) 🎉
Increment coverage report
Complete coverage report

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 11, 2025
@github-actions
Copy link
Contributor

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit 471f747 into apache:branch-4.0 Dec 17, 2025
23 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments