Skip to content

branch-4.1: [fix](cloud) Track deleted instance recycle status #66519 - #66667

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66519-branch-4.1
Aug 12, 2026
Merged

branch-4.1: [fix](cloud) Track deleted instance recycle status #66519#66667
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66519-branch-4.1

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #66519

@wyxxxcatYour Name
[fix](cloud) Track deleted instance recycle status (#66519)
50856f2
Introduce a persistent recycle state for deleted instances to split
instance recycling into separate data cleanup and metadata cleanup
stages.
The recycle process now transitions through:
```
DATA_CLEANUP_PENDING
-> METADATA_CLEANUP_PENDING
-> CLEANUP_COMPLETED
```
Each transition is persisted so that recycling can resume from the
latest state after failures or retries.
Also add an API to skip instance data cleanup by advancing the recycle
state directly from DATA_CLEANUP_PENDING to METADATA_CLEANUP_PENDING.
Subsequent recycle rounds will skip object data cleanup and continue
with metadata cleanup.
Repeated DROP operations preserve the existing recycle state instead of
resetting the recycle process.
@hello-stephen

hello-stephen commented Aug 11, 2026

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

hello-stephen commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

hello-stephen commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@hello-stephen

hello-stephen commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 100% (0/0) 🎉
Increment coverage report
Complete coverage report

@yiguolei
yiguolei merged commit 3d3ccc9 into branch-4.1Aug 12, 2026
29 of 32 checks passed
@github-actions

github-actionsBot commented Aug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

PR approved by at least one committer and no changes requested.

@github-actionsgithub-actionsBot added the approved Indicates a PR has been approved by one committer. label Aug 12, 2026
@github-actions

github-actionsBot commented Aug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

PR approved by anyone and no changes requested.

@morrySnow
morrySnow deleted the auto-pick-66519-branch-4.1 branch August 20, 2026 03:58
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguoleiyiguoleiyiguolei approved these changes

Assignees

No one assigned

Labels

approvedIndicates a PR has been approved by one committer.reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hello-stephen@yiguolei@wyxxxcat