-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[enhancement] Optimize the retry policy of backend request meta service #50957
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.
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
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
1 similar comment
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 33681 ms
|
TPC-DS: Total hot run time: 193632 ms
|
ClickBench: Total hot run time: 28.9 s
|
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ce (#50957) 1. Distinguish between request timeouts, connection timeouts, and business errors (transaction conflicts), and apply different retry configurations for each. 2. Reduce the number of retry attempts.
…ce (apache#50957) 1. Distinguish between request timeouts, connection timeouts, and business errors (transaction conflicts), and apply different retry configurations for each. 2. Reduce the number of retry attempts.
Uh oh!
There was an error while loading. Please reload this page.