-
Notifications
You must be signed in to change notification settings - Fork 967
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
ProxySQL2.0 is not sending COM_PING when multiplexing is disabled #2096
Comments
As I started this with Percona, I'd like to add this comment to Marcelo's description. To add to this, if the variable |
I didn't verify this yet, but I suspect a bug here. |
@renecannao when is this going to be fixed? |
Fixed in upcoming 2.0.6 |
Thanks @renecannao, do you have an ETA when 2.0.6 will be released |
Closing as fixed |
ProxySQL 2.0 is not refreshing connection from its pool if multiplexing is disabled.
How to repeat:
On Proxysql Admin interface:
On MySQL backend:
Make sure you don't have any backend connection already stablish otherwise the new timeouts won't take effect.
SELECT 1
stats_mysql_free_connections
that the connection came back to poolSHOW PROCESSLIST
directly on backend, you will see an idle connection that will be killed after 30sSELECT 1
At this point you will see an error in the proxysql log stating it tried to use a connection from the pool that was already closed by MySQL
Notes:
The text was updated successfully, but these errors were encountered: