Uh oh!
There was an error while loading. Please reload this page.
[Fix](warmup) one-time and periodic warm up job should be triggered regardless whether the rowset has been warmed up before - #56737
Conversation
hello-stephen
commented
Oct 9, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
4f683de to
7884d06Compare7884d06 to
72a1afbComparebobhan1
commented
Oct 9, 2025
run buildall |
bobhan1
commented
Oct 9, 2025
run buildall |
doris-robot
commented
Oct 9, 2025
ClickBench: Total hot run time: 30.18 s |
doris-robot
commented
Oct 9, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Oct 9, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
bobhan1
commented
Oct 9, 2025
run p0 |
hello-stephen
commented
Oct 9, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
| auto existing_state = _rowset_warm_up_states[rowset_id].state; | ||
| // For job-triggered warmup (one-time and periodic warmup), allow it to proceed | ||
| // except when there's already another job-triggered warmup in progress |
There was a problem hiding this comment.
what if the job-triigered warmup is done? still return false?
| } | ||
| _rowset_warm_up_states[rowset.rowset_id()] = { | ||
| .state = state, .num_segments = rowset.num_segments(), .start_tp = start_tp}; | ||
| _rowset_warm_up_states[rowset_id] = { |
There was a problem hiding this comment.
Since two different trigger types will share the same states (and the same counter in it), will this replacement of elements in the map interfere with other warmup types with the same rowsetid?
There was a problem hiding this comment.
only one trigger source can update a rowset's state in any time
8d9b99d to
6f27bc2Comparebobhan1
commented
Oct 10, 2025
run buildall |
doris-robot
commented
Oct 10, 2025
TPC-DS: Total hot run time: 189701 ms |
doris-robot
commented
Oct 10, 2025
ClickBench: Total hot run time: 30.42 s |
bobhan1
commented
Oct 10, 2025
run cloud_p0 |
bobhan1
commented
Oct 10, 2025
run nonConcurrent |
doris-robot
commented
Oct 10, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Oct 10, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
1 similar comment
hello-stephen
commented
Oct 10, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
PR approved by at least one committer and no changes requested. |
Uh oh!
There was an error while loading. Please reload this page.
What problem does this PR solve?
Related PR: #54611
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)