-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[conf](mysql) opt mysql network timeout to 600s #32545
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. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
run external |
|
run buildall |
|
run buildall |
TPC-H: Total hot run time: 37953 ms |
TPC-DS: Total hot run time: 181138 ms |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
xy720
left a comment
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. |
* [fix](mysql) fix mysql channel infinite blocking (#28808) Call the Channels blocking method with timeout instead. Using session variables net_write_timeout and net_read_timeout as the timeout parameter. * [conf](mysql) opt mysql network timeout to 600s #32545 --------- Co-authored-by: fornaix <foxnaix@gmail.com>
Proposed changes
Now
netWriteTimeoutandnetReadTimeoutonly used inMysqlChannel, from pr: #28808First of all, mysql client may be in different location as FE, the network maybe slow, not like FE and BE always have a fast network.
Secondly, the max packet size is 16MB in Mysql Protocol, not very small.
So we should enlarge this timeout.
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...