Skip to content

branch-4.0: [enhance](job) delay load task schedule when transaction fail #57092 #57131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yiguolei merged 1 commit into from
Oct 20, 2025
Merged

branch-4.0: [enhance](job) delay load task schedule when transaction fail #57092 #57131

yiguolei merged 1 commit into from
Oct 20, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 19, 2025

Cherry-picked from #57092

@sollhui
[enhance](job) delay load task schedule when transaction fail (#57092)
3a06255 
Now, when transaction fail, routine load task will retry as soon as
possible, when meet some temporarily unrecoverable errors like
`too_many_version`, it will retry too many times in a short time and
take huge pressure to upstream system like Kafka.

To solve this problem, we delay load task schedule when transaction fail
to reduce retry times when meet error and restore normal schedule if
transactions resume normal execution.
@github-actions github-actions bot requested a review from yiguolei as a code owner October 19, 2025 08:54
@Thearas
Copy link
Contributor

Thearas commented Oct 19, 2025

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 Oct 19, 2025
@Thearas
Copy link
Contributor

Thearas commented Oct 19, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Oct 19, 2025

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Oct 20, 2025
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 20, 2025

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 20, 2025

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit c046ff8 into branch-4.0 Oct 20, 2025
25 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-57092-branch-4.0 branch October 20, 2025 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@Thearas @hello-stephen @yiguolei @dataroaring @sollhui