Skip to content

branch-4.1: [fix](fetype) Commit FE type only after transition completes #68302 - #68325

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-68302-branch-4.1
Open

github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-68302-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #68302

### What problem does this PR solve?

Problem Summary:

A non-master FE transition can be interrupted when a newer BDB state is
queued while the listener waits for metadata readiness. The listener
previously still committed the target FE type even though non-master
initialization, including MetricRepo.init(), had not run. A repeated
FOLLOWER or OBSERVER notification was then treated as redundant, leaving
the FE in an incompletely initialized state.

This change makes transferToNonMaster() report whether the transition
completed and updates feType only after all initialization finishes. An
interrupted transition retains the previous committed state so the
queued event is evaluated against the state that was actually
initialized and can retry the transition.

### Release note

Fix FE state transitions that could leave a follower or observer serving
queries before non-master initialization completed.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner September 21, 2026 08:18
@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?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 50.00% (6/12) 🎉
Increment coverage report
Complete coverage report

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.

2 participants