Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Can't create more than max_prepared_stmt_count statements #1251
ProxySQL Version: proxysql-1.4.3-1-centos67.x86_64.rpm
Laravel use prepared statement default.
This's a emergency that happened in my production:
my backend db status:
In my other db instances that have no proxysql frontend,
By the way, all
Hi @seanlook .
Short answer: increase
ProxySQL optimizes this, tracking all
This is true, ProxySQL does not close statements, never.
Can you copy the output of
All my proxysql nodes show
If I have high concurrency in a shot time, would not closing the prepared statement backend is a problem?
Thank you for the output.
What can happen is that if you have a lot of connections, they will sum up. For example, if you have 20 prepared statements prepared in 80 connections, that is 16000 prepared statements (very close to the default limit
To sum up:
Hi @renecannao ,
I appreciate it that let the user decide whether use the feature to boost performance or not.
I eccounter the problem in production today again, and it's really a disaster for me. I had set
Would you provide a parameter to disable or enable this kind of prepared statement behavior?
@seanlook : disabling this feature is not an option right now, and isn't easy to implement.
What is your current value of
Re-opening the issue.
The current value of
There is 3 ProxySQL nodes connected to backend server.
I have restarted proxysql , so
3 nodes times 5000
But more than
How is it possible that Stmt_Server_Active_Total went all the way up to 16.5k:
When max amount of connections to all nodes would be 600 (3 nodes, 200 per node)
and max_stmts_per_connection was at default of 20
Sounds like it's leaking statements when resetting the connection?