Skip to content

branch-4.1: [fix](cloud) Fix balanced_tablets_shards leak memory and fix some file cache case #59093#61575

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

branch-4.1: [fix](cloud) Fix balanced_tablets_shards leak memory and fix some file cache case #59093#61575
github-actions[bot] wants to merge 1 commit intobranch-4.1from
auto-pick-59093-branch-4.1

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #59093

…e cache case (#59093)

### What problem does this PR solve?
1. When fixing the issue of CloudWarmUpManager leaking a small amount of
memory and failing to remove (tablet_id, peer_addr) from memory during
warm-up balance when file cache meta is not retrieved from source, the
issue was resolved.
2. Fixed several file cache Docker cases affected by small file
optimization PR(#57770)


Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

### 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.
        - [x] Previous test can cover this change.
        - [ ] No code files have been changed.
        - [ ] Other reason <!-- Add your reason?  -->

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

- Does this need documentation?
    - [x] 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 March 20, 2026 10:01
@Thearas
Copy link
Contributor

Thearas commented Mar 20, 2026

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 Mar 20, 2026
@Thearas
Copy link
Contributor

Thearas commented Mar 20, 2026

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/26) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.56% (19419/36944)
Line Coverage 36.05% (181357/503140)
Region Coverage 32.53% (140388/431544)
Branch Coverage 33.48% (61225/182890)

@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 0.00% (0/26) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 71.06% (25699/36164)
Line Coverage 53.93% (270482/501497)
Region Coverage 51.52% (224411/435582)
Branch Coverage 52.82% (96911/183458)

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.

4 participants