Skip to content

branch-4.1: [fix](cloud) Prevent urgent load from preempting schema change lock #66082 - #66226

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

branch-4.1: [fix](cloud) Prevent urgent load from preempting schema change lock #66082#66226
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66082-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #66082

…66082)

Related PR: #53086

Problem Summary: Urgent MOW load lock requests currently replace any
existing delete bitmap update lock after the force-take threshold. If a
heavy schema change owns the lock, the load can invalidate the schema
change and make its later commit fail. This change keeps active schema
change locks protected in both v1 and v2 lock implementations. Urgent
loads continue to preempt compaction and load locks, and stale schema
change locks still follow the existing expiration cleanup path.

The unit-test matrix directly verifies persisted lock ownership and v2
job-key cleanup for active schema change, expired schema change,
compaction, and ordinary load owners. An isolated cloud Docker case
pauses schema change after lock acquisition, limits the urgent load to
two immediate lock attempts, and verifies that the load fails with the
lock conflict while schema change retains ownership.

### Release note

Urgent MOW loads no longer preempt active schema change delete bitmap
locks.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner July 29, 2026 07:51
@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

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