Skip to content

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #59390

…in _unused_rowsets map (#59390)

### What problem does this PR solve?

`_clean_unused_rowset_metas` could incorrectly remove rowset metas (and
its delete_bitmap) that are still tracked in the `_unused_rowsets` map,
which holds rowsets pending deletion.
The fix adds a check to skip these rowsets during cleanup, preventing
premature removal of `_unused_rowsets`. Otherwise, if query a mow table
with rowsets in `_unused_rowsets` map, and `_clean_unused_rowset_metas`
delete delete_bitmap of these rowset, will get duplicated keys.

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [ ] Regression test
    - [ ] Unit Test
    - [ ] Manual test (add detailed scripts or steps below)
    - [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
        - [ ] Previous test can cover this change.
        - [ ] No code files have been changed.
        - [ ] Other reason <!-- Add your reason?  -->

- Behavior changed:
    - [ ] No.
    - [ ] Yes. <!-- Explain the behavior change -->

- Does this need documentation?
    - [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
apache/doris-website#1214 -->

### Check List (For Reviewer who merge this PR)

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->
@github-actions github-actions bot requested a review from yiguolei as a code owner December 26, 2025 17:59
@hello-stephen
Copy link
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?

@dataroaring dataroaring reopened this Dec 26, 2025
@hello-stephen
Copy link
Contributor

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 66.67% (4/6) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.27% (18601/34916)
Line Coverage 39.02% (172227/441326)
Region Coverage 33.74% (133283/395077)
Branch Coverage 34.71% (57584/165924)

@mymeiyi
Copy link
Contributor

mymeiyi commented Dec 27, 2025

run nonConcurrent

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.

3 participants