Skip to content

branch-4.1: [fix](group commit) fix can not get a block queue #63722#65078

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

branch-4.1: [fix](group commit) fix can not get a block queue #63722#65078
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63722-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #63722

Under high-concurrency async stream load, group commit may fail to get a
block queue when creating the group commit plan fragment fails or leaves
pending load requests waiting for a queue that is no longer usable. This
change tracks pending create-plan requests per table, adds a background
worker to resubmit group commit plan creation, and introduces
group_commit_create_plan_timeout_ms so waiting requests can be released
after a bounded time.
@github-actions github-actions Bot requested a review from yiguolei as a code owner July 1, 2026 06:38
@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

@mymeiyi

mymeiyi commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

run cloud_p0

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 10.90% (29/266) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 64.23% (23951/37290)
Line Coverage 47.73% (247988/519605)
Region Coverage 45.24% (205770/454817)
Branch Coverage 46.20% (88724/192038)

1 similar comment
@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 10.90% (29/266) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 64.23% (23951/37290)
Line Coverage 47.73% (247988/519605)
Region Coverage 45.24% (205770/454817)
Branch Coverage 46.20% (88724/192038)

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