Skip to content

branch-3.1: [Opt](cloud-mow) Skip MS RPC retry's backoff when encounter fdb txn conflict when mow load get ms delete bitmap lock #52360 - #52437

Merged
morrySnow merged 1 commit into
branch-3.1from
auto-pick-52360-branch-3.1
Jun 30, 2025
Merged

branch-3.1: [Opt](cloud-mow) Skip MS RPC retry's backoff when encounter fdb txn conflict when mow load get ms delete bitmap lock #52360#52437
morrySnow merged 1 commit into
branch-3.1from
auto-pick-52360-branch-3.1

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Jun 27, 2025

Copy link
Copy Markdown
Contributor

Cherry-picked from #52360

@bobhan1Your Name
[Opt](cloud-mow) Skip MS RPC retry's backoff when encounter fdb txn c…
c3f328a
…onflict when mow load get ms delete bitmap lock (#52360)
### What problem does this PR solve?
Let mow load txn skip MS RPC framework's backoff sleep time and totally
let FE control the backoff time to reduce latency long tail.
Test environment: cloud mode, 1 FE, 3 BE(8C 32GB), 5 threads, 120
buckets, 50rows/per load, cumu threads=8
#### Before
|
![](https://github.com/user-attachments/assets/9d3f80d2-e56e-4153-9247-cddb05e68216)
|
![](https://github.com/user-attachments/assets/d5221f07-ffd4-439b-8125-b4f854887973)
|
|-----------------|-----------------|
#### After
|
![](https://github.com/user-attachments/assets/7ff3d899-9828-4a38-bbaf-62abbd9718d2)
|
![](https://github.com/user-attachments/assets/99fdb83e-bf59-4f24-82f0-9c8557463c29)
|
|-----------------|-----------------|
@Thearas

Thearas commented Jun 27, 2025

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?

@Thearas

Thearas commented Jun 27, 2025

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

hello-stephen commented Jun 27, 2025

Copy link
Copy Markdown
Contributor

Cloud UT Coverage Report

Increment line coverage 33.33% (1/3) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage83.46% (1130/1354)
Line Coverage67.27% (19660/29225)
Region Coverage67.29% (9985/14839)
Branch Coverage56.95% (5276/9264)

@morrySnow
morrySnow merged commit 795c994 into branch-3.1Jun 30, 2025
@github-actions
github-actionsBot deleted the auto-pick-52360-branch-3.1 branch June 30, 2025 10:56
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnowmorrySnowmorrySnow approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@Thearas@hello-stephen@morrySnow@dataroaring@bobhan1