-
Notifications
You must be signed in to change notification settings - Fork 287
Fixed a bug that caused the system to stuck after packet loss during data loading #23390
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: 3.0-dev
Are you sure you want to change the base?
Conversation
fengttt
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.
In general I don't think tweaking timeout is the right fix for a system hung.
What is the real "case" for hung? And what error we generate?
The real stuck during the load phase is here: https://github.com/matrixorigin/matrixone/blob/main/pkg/frontend/mysql_buffer.go#L569. Because the read timeout is 24 hours, if the connection isn't closed, the read operation will get stuck indefinitely, repeatedly returning an EOF error after 4 hours or 40 minutes. |
What type of PR is this?
Which issue(s) this PR fixes:
issue https://github.com/matrixorigin/MO-Cloud/issues/6448
What this PR does / why we need it:
Fixed a bug that caused the system to stuck after packet loss during data loading
The network read timeout is 24 hours; if packets are lost, it will wait indefinitely.