-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](job) fix routine load task scheduler block for one job can not find any BE #52654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
a9d926e to
ed83b14
Compare
|
run buildall |
liaoxin01
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 34881 ms |
FE UT Coverage ReportIncrement line coverage |
TPC-DS: Total hot run time: 185697 ms |
ClickBench: Total hot run time: 29.89 s |
ed83b14 to
ce01328
Compare
|
run buildall |
ce01328 to
f6f4eb2
Compare
|
run buildall |
f6f4eb2 to
b1115a3
Compare
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
TPC-H: Total hot run time: 33788 ms |
TPC-DS: Total hot run time: 184778 ms |
ClickBench: Total hot run time: 29.63 s |
FE UT Coverage ReportIncrement line coverage |
MoanasDaddyXu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…find any BE (#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck.
…find any BE (#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck.
…find any BE (apache#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck.
…find any BE (apache#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck.
… find any BE (apache#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck.
…find any BE (apache#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck.
…find any BE (apache#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck.
…job can not find any BE (#52654) (#52791) pick (#52654) ### What problem does this PR solve? routine load task will block in following case: 1. The user created a job using the admin user of clusterA, and at some point deleted clusterA, and renamed clusterB to clusterA 2. The cluster ID saved in the job is invalid and can't find any BE 3. This task was repeatedly taken out of the queue and was put back to queue for there was no BE to execute, causing the other tasks to get stuck. ### What problem does this PR solve? Issue Number: close #xxx Related PR: #xxx Problem Summary: ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] 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 <!-- Add your reason? --> - Behavior changed: - [ ] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [ ] No. - [ ] Yes. <!-- Add document PR link here. eg: apache/doris-website#1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into -->
What problem does this PR solve?
routine load task will block in following case:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)