[opt](routine load) optimize routine load timeout logic#40818
Merged
liaoxin01 merged 1 commit intoapache:masterfrom Sep 19, 2024
sollhui:opt_rl_timeout
Merged
[opt](routine load) optimize routine load timeout logic#40818liaoxin01 merged 1 commit intoapache:masterfrom sollhui:opt_rl_timeout
liaoxin01 merged 1 commit intoapache:masterfrom
sollhui:opt_rl_timeout
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 42836 ms |
TPC-DS: Total hot run time: 193802 ms |
ClickBench: Total hot run time: 31.73 s |
liaoxin01
reviewed
Sep 13, 2024
Contributor
Author
|
run buildall |
1 similar comment
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 43433 ms |
TPC-DS: Total hot run time: 192024 ms |
ClickBench: Total hot run time: 31.14 s |
Contributor
Author
|
run buildall |
3 similar comments
Contributor
Author
|
run buildall |
Contributor
Author
|
run buildall |
Contributor
Author
|
run buildall |
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
Author
|
run buildall |
github-actions
bot
removed
the
approved
Contributor
Author
|
run buildall |
1 similar comment
Contributor
Author
|
run buildall |
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 41204 ms |
TPC-DS: Total hot run time: 198691 ms |
ClickBench: Total hot run time: 31.04 s |
liaoxin01
approved these changes
Sep 18, 2024
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
dataroaring
pushed a commit
that referenced
this pull request
Sep 19, 2024
If IO/CPU resources are tight, routine load task is likely to timeout. The current method is self-adaption backoff #32227, but the problem is it will do some ineffective work to match proper timeout. For one routine load task, a better way to handle task is finishing executing instead of retry when resources are tight. Therefore, this pr increase timeout to make "task always finish even if it is slow when resources are tight".
This was referenced Sep 23, 2024
liaoxin01
pushed a commit
that referenced
this pull request
Sep 25, 2024
) pick #40818 If IO/CPU resources are tight, routine load task is likely to timeout. The current method is self-adaption backoff #32227, but the problem is it will do some ineffective work to match proper timeout. For one routine load task, a better way to handle task is finishing executing instead of retry when resources are tight. Therefore, this pr increase timeout to make "task always finish even if it is slow when resources are tight".
dataroaring
pushed a commit
that referenced
this pull request
Sep 26, 2024
) pick (#40818) If IO/CPU resources are tight, routine load task is likely to timeout. The current method is self-adaption backoff #32227, but the problem is it will do some ineffective work to match proper timeout. For one routine load task, a better way to handle task is finishing executing instead of retry when resources are tight. Therefore, this pr increase timeout to make "task always finish even if it is slow when resources are tight".
dataroaring
added
dev/2.0.16-merged-deprecated
Closed
16 tasks
liaoxin01
pushed a commit
that referenced
this pull request
Apr 28, 2025
… value (#50478) High priority load task was introduced to avoid load timeout with short execution times, which mainly for routine load tasks, now the timeout time for routine load tasks has been is set to 10 times the max_match_interval (#40818), so the default value of load_task_high_priority_threshold_second should also be increased.
github-actions bot
pushed a commit
that referenced
this pull request
Apr 28, 2025
… value (#50478) High priority load task was introduced to avoid load timeout with short execution times, which mainly for routine load tasks, now the timeout time for routine load tasks has been is set to 10 times the max_match_interval (#40818), so the default value of load_task_high_priority_threshold_second should also be increased.
github-actions bot
pushed a commit
that referenced
this pull request
Apr 28, 2025
… value (#50478) High priority load task was introduced to avoid load timeout with short execution times, which mainly for routine load tasks, now the timeout time for routine load tasks has been is set to 10 times the max_match_interval (#40818), so the default value of load_task_high_priority_threshold_second should also be increased.
koarz
pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
… value (apache#50478) High priority load task was introduced to avoid load timeout with short execution times, which mainly for routine load tasks, now the timeout time for routine load tasks has been is set to 10 times the max_match_interval (apache#40818), so the default value of load_task_high_priority_threshold_second should also be increased.
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
4 participants
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.
If IO/CPU resources are tight, routine load task is likely to timeout. The current method is self-adaption backoff #32227, but the problem is it will do some ineffective work to match proper timeout. For one routine load task, a better way to handle task is finishing executing instead of retry when resources are tight. Therefore, this pr increase timeout to make "task always finish even if it is slow when resources are tight".