Skip to content

branch-2.1: [opt](blacklist) Backend should not be added to blacklist easily #41170 #49125

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
Closed
zhiqiang-hhhh wants to merge 1 commit into from
Closed

branch-2.1: [opt](blacklist) Backend should not be added to blacklist easily #41170 #49125

zhiqiang-hhhh wants to merge 1 commit into from

Conversation

@zhiqiang-hhhh
Copy link
Contributor

@zhiqiang-hhhh zhiqiang-hhhh commented Mar 17, 2025

cherry pick from #41170

@zhiqiang-hhhh
[opt](blacklist) Backend should not be added to blacklist easily (apa…
91492f9 
…che#41170)

To avoid false negative, backend will be added to black list when:
* Try to add this backend multiple times(10) in
`do_add_backend_black_list_threshold_secs`.

Backend will stay in black list in
`stay_in_backend_black_list_threshold_secs` or it is alive.
@zhiqiang-hhhh zhiqiang-hhhh requested a review from yiguolei as a code owner March 17, 2025 02:28
@zhiqiang-hhhh
Copy link
Contributor Author

zhiqiang-hhhh commented Mar 17, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Mar 17, 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?

@yiguolei
Copy link
Contributor

yiguolei commented Mar 17, 2025

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei Awaiting requested review from yiguolei yiguolei is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@zhiqiang-hhhh @hello-stephen @yiguolei