-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[Enhancement](BRPC)enlarge brpc_max_body_size to avoid connection killed #51896
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
base: master
Are you sure you want to change the base?
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
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
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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
run buildall |
TPC-H: Total hot run time: 34129 ms
|
TPC-DS: Total hot run time: 186008 ms
|
ClickBench: Total hot run time: 29.49 s
|
What problem does this PR solve?
In our env(180BE), the default brpc_max_body_size(3G) is not OK, which cause query/load failed. change it to 6G is OK now. so change the default brpc_max_body_size to 6G.
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)