-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[enhance](job) optimize auto resume rule to adapt VCG failover #59421
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 |
TPC-H: Total hot run time: 35319 ms |
TPC-DS: Total hot run time: 180070 ms |
ClickBench: Total hot run time: 27.26 s |
FE UT Coverage ReportIncrement line coverage `` 🎉 |
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. |
dataroaring
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
### What problem does this PR solve? In #52515 introduces VCG(Virtual Compute Group) to be used for multi availability zone disaster recovery. But routine load job do not adapt it perfectly: If a cluster in an availability zone crashes, VCG provides disaster recovery capabilities, but the job will not be automatically resume. So this PR removed the `dead BE count` calculation when judge `isNeedAutoSchedule`. ### Release note None
### What problem does this PR solve? In #52515 introduces VCG(Virtual Compute Group) to be used for multi availability zone disaster recovery. But routine load job do not adapt it perfectly: If a cluster in an availability zone crashes, VCG provides disaster recovery capabilities, but the job will not be automatically resume. So this PR removed the `dead BE count` calculation when judge `isNeedAutoSchedule`. ### Release note None
…lover #59421 (#59424) Cherry-picked from #59421 Co-authored-by: hui lai <[email protected]>
What problem does this PR solve?
In #52515 introduces VCG(Virtual Compute Group) to be used for multi availability zone disaster recovery.
But routine load job do not adapt it perfectly: If a cluster in an availability zone crashes, VCG provides disaster recovery capabilities, but the job will not be automatically resume. So this PR removed the
dead BE countcalculation when judgeisNeedAutoSchedule.Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)