Skip to content

branch-4.1: [fix](cloud) Exclude stale rowsets from schema change temporary tablet #67351 - #67383

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

branch-4.1: [fix](cloud) Exclude stale rowsets from schema change temporary tablet #67351#67383
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-67351-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #67351

#67351)

### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: During merge-on-write cloud schema changes, the
delete-bitmap temporary tablet copied stale rowset metadata from the
real shadow tablet. Its version tracker could select a compacted stale
edge that was absent from the active rowset map, causing schema change
to fail with a rowset capture error under concurrent writes and
compaction. Clear only the copied stale rowset metadata before
constructing the temporary tablet so its tracker is built exclusively
from active schema-change output and incremental rowsets, without
altering the source tablet or shared delete-bitmap cache.

### Release note

Fix cloud merge-on-write schema changes that could fail during
concurrent writes and compaction.

### Check List (For Author)

- Test: Unit Test
    - `./run-be-ut.sh --run --filter=CloudSchemaChangeJobTest.* -j 48`
    - `./build.sh --be -j 48`
- Behavior changed: Yes. Cloud schema change temporary tablets no longer
inherit stale rowset metadata.
- Does this need documentation: No
@github-actions
github-actions Bot requested a review from yiguolei as a code owner September 1, 2026 10:20
@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