Uh oh!
There was an error while loading. Please reload this page.
[improve](routine load) improve routine load observability - #46238
Merged
Conversation
Thearas
commented
Jan 1, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
sollhui
commented
Jan 1, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 1, 2025
TPC-H: Total hot run time: 32703 ms |
doris-robot
commented
Jan 1, 2025
TPC-DS: Total hot run time: 197047 ms |
doris-robot
commented
Jan 1, 2025
ClickBench: Total hot run time: 31.79 s |
sollhuiforce-pushed
the
improve_rl_observability
branch
from
January 2, 2025 04:56
e14a130 to
39089e6Comparesollhui
commented
Jan 2, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 2, 2025
TPC-H: Total hot run time: 32931 ms |
doris-robot
commented
Jan 2, 2025
TPC-DS: Total hot run time: 196550 ms |
doris-robot
commented
Jan 2, 2025
ClickBench: Total hot run time: 30.83 s |
sollhuiforce-pushed
the
improve_rl_observability
branch
from
January 2, 2025 14:06
39089e6 to
56b84baComparesollhui
commented
Jan 2, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 2, 2025
TPC-H: Total hot run time: 32637 ms |
doris-robot
commented
Jan 2, 2025
TPC-DS: Total hot run time: 197974 ms |
doris-robot
commented
Jan 2, 2025
ClickBench: Total hot run time: 31.75 s |
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
github-actionsBot
pushed a commit
that referenced
this pull request
Jan 7, 2025
1. **reset other msg in the a stream window** The routine load job is a continuously scheduled job, and as the job runs, previous errors do not need to be constantly displayed. 2. **show error info when transaction of sub task failed** If a subtask fails, it will continuously retry, and there may be some errors that prevent the job from scheduling and consuming data properly, such as continuous too many segments error(code: -235). At this time, it is necessary to display it in a timely manner to make the user aware. 3. **set pause reason to other msg when reschedule job** For jobs that are unexpectedly paused, the job manager has an auto resume mechanism. However, for some scenarios, such as not being able to connect to Kafka and being auto resumed after pause to retry, it may cause users to not see the problem for a long time. Unexpectedly paused jobs always have issues, even if auto resume occurs, the reason for the error needs to be displayed.
github-actionsBot
pushed a commit
that referenced
this pull request
Jan 7, 2025
1. **reset other msg in the a stream window** The routine load job is a continuously scheduled job, and as the job runs, previous errors do not need to be constantly displayed. 2. **show error info when transaction of sub task failed** If a subtask fails, it will continuously retry, and there may be some errors that prevent the job from scheduling and consuming data properly, such as continuous too many segments error(code: -235). At this time, it is necessary to display it in a timely manner to make the user aware. 3. **set pause reason to other msg when reschedule job** For jobs that are unexpectedly paused, the job manager has an auto resume mechanism. However, for some scenarios, such as not being able to connect to Kafka and being auto resumed after pause to retry, it may cause users to not see the problem for a long time. Unexpectedly paused jobs always have issues, even if auto resume occurs, the reason for the error needs to be displayed.
yiguolei pushed a commit
that referenced
this pull request
Jan 8, 2025
1. **reset other msg in the a stream window** The routine load job is a continuously scheduled job, and as the job runs, previous errors do not need to be constantly displayed. 2. **show error info when transaction of sub task failed** If a subtask fails, it will continuously retry, and there may be some errors that prevent the job from scheduling and consuming data properly, such as continuous too many segments error(code: -235). At this time, it is necessary to display it in a timely manner to make the user aware. 3. **set pause reason to other msg when reschedule job** For jobs that are unexpectedly paused, the job manager has an auto resume mechanism. However, for some scenarios, such as not being able to connect to Kafka and being auto resumed after pause to retry, it may cause users to not see the problem for a long time. Unexpectedly paused jobs always have issues, even if auto resume occurs, the reason for the error needs to be displayed.
yiguolei pushed a commit
that referenced
this pull request
Jan 8, 2025
1. **reset other msg in the a stream window** The routine load job is a continuously scheduled job, and as the job runs, previous errors do not need to be constantly displayed. 2. **show error info when transaction of sub task failed** If a subtask fails, it will continuously retry, and there may be some errors that prevent the job from scheduling and consuming data properly, such as continuous too many segments error(code: -235). At this time, it is necessary to display it in a timely manner to make the user aware. 3. **set pause reason to other msg when reschedule job** For jobs that are unexpectedly paused, the job manager has an auto resume mechanism. However, for some scenarios, such as not being able to connect to Kafka and being auto resumed after pause to retry, it may cause users to not see the problem for a long time. Unexpectedly paused jobs always have issues, even if auto resume occurs, the reason for the error needs to be displayed.
yiguolei pushed a commit
that referenced
this pull request
Jan 10, 2025
dataroaring pushed a commit
that referenced
this pull request
Jan 13, 2025
7 tasks
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 freeto 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?
related #48511
reset other msg in the a stream window
The routine load job is a continuously scheduled job, and as the job runs, previous errors do not need to be constantly displayed.
show error info when transaction of sub task failed
If a subtask fails, it will continuously retry, and there may be some errors that prevent the job from scheduling and consuming data properly, such as continuous too many segments error(code: -235). At this time, it is necessary to display it in a timely manner to make the user aware.
set pause reason to other msg when reschedule job
For jobs that are unexpectedly paused, the job manager has an auto resume mechanism. However, for some scenarios, such as not being able to connect to Kafka and being auto resumed after pause to retry, it may cause users to not see the problem for a long time. Unexpectedly paused jobs always have issues, even if auto resume occurs, the reason for the error needs to be displayed.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)