Skip to content

branch-4.1: [fix](fe) Clear warmup jobs on available backends (#62931)#63029

Merged
yiguolei merged 1 commit intoapache:branch-4.1from
bobhan1:branch-4.1-pick-doris-62931
May 7, 2026
Merged

branch-4.1: [fix](fe) Clear warmup jobs on available backends (#62931)#63029
yiguolei merged 1 commit intoapache:branch-4.1from
bobhan1:branch-4.1-pick-doris-62931

Conversation

@bobhan1
Copy link
Copy Markdown
Contributor

@bobhan1 bobhan1 commented May 6, 2026

pick #62931

Problem Summary: CORE-6050 reports that canceling a cloud warm up job can fail to notify surviving BEs when client initialization fails on an unavailable BE. Keep the normal warmup RPC path fail-fast, but make CLEAR_JOB client initialization skip unavailable BEs and continue clearing reachable BEs.

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • 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
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

Problem Summary: CORE-6050 reports that canceling a cloud warm up job
can fail to notify surviving BEs when client initialization fails on an
unavailable BE. Keep the normal warmup RPC path fail-fast, but make
CLEAR_JOB client initialization skip unavailable BEs and continue
clearing reachable BEs.
@bobhan1 bobhan1 requested a review from yiguolei as a code owner May 6, 2026 10:40
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@bobhan1
Copy link
Copy Markdown
Contributor Author

bobhan1 commented May 6, 2026

run buildall

@yiguolei yiguolei merged commit 58044fc into apache:branch-4.1 May 7, 2026
29 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants