[fix](job) fix routine load task transaction timeout error#59999
Merged
JNSimba merged 1 commit intoapache:masterfrom Jan 20, 2026
Merged
[fix](job) fix routine load task transaction timeout error#59999JNSimba merged 1 commit intoapache:masterfrom
JNSimba merged 1 commit intoapache:masterfrom
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 31398 ms |
TPC-DS: Total hot run time: 174679 ms |
ClickBench: Total hot run time: 26.92 s |
e5c0fcf to
a0498c6
Compare
Contributor
Author
|
run buildall |
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 31285 ms |
TPC-DS: Total hot run time: 174026 ms |
ClickBench: Total hot run time: 27.05 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
a0498c6 to
7cb802b
Compare
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 31829 ms |
TPC-DS: Total hot run time: 173475 ms |
ClickBench: Total hot run time: 26.79 s |
Contributor
FE Regression Coverage ReportIncrement line coverage |
1 similar comment
Contributor
FE Regression Coverage ReportIncrement line coverage |
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
JNSimba
approved these changes
Jan 20, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Jan 20, 2026
### What problem does this PR solve? ## Problem When routine load uses adaptive batch interval (introduced in #56930), the FE transaction timeout does not match the BE task timeout, causing transactions to be aborted by `txnCleaner` while BE is still processing. ### Root Cause In `RoutineLoadTaskScheduler.scheduleOneTask()`, the execution order is: 1. `beginTxn()` - creates transaction with **original** `timeoutMs` 2. `createRoutineLoadTask()` → `adaptiveBatchParam()` - updates `timeoutMs` to **adaptive** value This causes a mismatch: - FE transaction timeout: original value (e.g., 200 seconds) - BE task timeout: adaptive value (e.g., 360 seconds)
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?
Problem
When routine load uses adaptive batch interval (introduced in #56930), the FE transaction timeout does not match the BE task timeout, causing transactions to be aborted by
txnCleanerwhile BE is still processing.Root Cause
In
RoutineLoadTaskScheduler.scheduleOneTask(), the execution order is:beginTxn()- creates transaction with originaltimeoutMscreateRoutineLoadTask()→adaptiveBatchParam()- updatestimeoutMsto adaptive valueThis causes a mismatch:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)