Skip to content

branch-4.0: [fix](cloud) Refresh base tablet before schema change V1 #64312#64429

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

branch-4.0: [fix](cloud) Refresh base tablet before schema change V1 #64312#64429
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64312-branch-4.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64312

Related PR: #62272

Problem Summary: Cloud schema change retries could keep registering a
stale alter version after a cross-V1 compaction conflict. The retry path
synced the base tablet only up to the request alter version, so a local
base tablet whose max version already exceeded that request could skip
refreshing newer visible rowsets. When a new schema-change tablet had a
compaction rowset crossing the stale V1, every retry reused that V1 and
eventually exhausted the retry limit.

This change refreshes the base tablet without capping sync by the
request alter version before computing schema change V1, allowing
retries to register a fresh boundary. It also adds a docker regression
case that blocks schema change, creates a cross-V1 retry, injects stale
local max-version state for query-version sync, and verifies the retry
finishes after the base tablet is refreshed.

### Release note

Fix cloud schema change retry stale V1 failure.
@github-actions github-actions Bot requested a review from morningman as a code owner June 11, 2026 11:57
@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

BE UT Coverage Report

Increment line coverage 0.00% (0/12) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.33% (19453/36480)
Line Coverage 36.44% (181790/498841)
Region Coverage 33.03% (141205/427523)
Branch Coverage 33.90% (61127/180332)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (12/12) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 71.40% (25499/35711)
Line Coverage 54.28% (270306/497967)
Region Coverage 51.92% (224201/431841)
Branch Coverage 53.28% (96419/180965)

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