Skip to content

branch-4.0: [fix](cloud) Avoid deleting nonexistent delete bitmap files #62967#63015

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

branch-4.0: [fix](cloud) Avoid deleting nonexistent delete bitmap files #62967#63015
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-62967-branch-4.0

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 6, 2026

Cherry-picked from #62967

When recycling rowset data, the recycler treated a missing versioned delete bitmap meta key as "not packed" and added the standalone delete bitmap object path to the delete_files request. This caused unnecessary delete object requests for `<rowset_id>_delete_bitmap.db` even when no delete bitmap storage metadata existed.

The fix makes delete bitmap storage handling explicit: missing meta, FDB storage, standalone file storage, and packed file storage are distinguished. The recycler now only deletes `<rowset_id>_delete_bitmap.db` when the metadata explicitly indicates a standalone delete bitmap file.
@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