-
Notifications
You must be signed in to change notification settings - Fork 972
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
A large query triggers oom, help #1990
Comments
Online, thank you |
Is the query using binary protocol (prepared statement) or text protocol? |
hi. |
I am using this package |
If the client is using prepared statements, currently proxysql cannot throttle traffic. I think we need to introduce a new variable to define how much data can be buffered before aborting the request. |
I am looking forward to this parameter, thanks. It should be session level |
Can you clarify the limitation that requires the need to return the full dataset? |
hi:
When the query returns a large amount of data, it will trigger the system's OOM。The proxysql process will be killed。
This issue exists in the following versions.
This should be because proxysql receives data faster than the client consumes.
I executed a query with about 20 million data volumes.
As shown below:
I adjusted the parameter mysql-throttle_max_bytes_per_second_to_client and it didn't work.
I read the relevant questions, but did not solve them, ask for advice, thank you
The text was updated successfully, but these errors were encountered: