-
Notifications
You must be signed in to change notification settings - Fork 982
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
ProxySQL does not automatically reopen backend connections when the last executed query was an INSERT that generated an auto-increment #3923
Comments
I think the subject of this issue should be: "[...] was an INSERT that generated an auto-increment" . |
After some testing we can confirm that |
Hey,
I am experiencing some behavior, that looks like a bug to me:
When I
KILL <process id>
in a separate MySQL connectionSELECT * FROM mytable
I get the following error in the mysql client CLI:
I would expect ProxySQL to reconnect to MySQL automatically without the client actually noticing anything.
I am running ProxySQL
2.4.2
on Ubuntu 20. My MySQL version is8.0.27-18.1
.The MySQL-Cluster actually is a Galera Cluster, but as only one host is used and no read-write-splitting is configured, this should not matter.
And apparently in the exact same setup, ProxySQL does exactly this, when the last executed statement on the connection was a
SELECT
statement.So the following combination works fine:
SELECT * FROM mytable
KILL <process id>
in a separate MySQL connectionSELECT * FROM mytable
In this combination you will not see any error message in the client, as ProxySQL reconnect the backend connection automatically.
mySQL Servers:
Global Variables:
Galera Hostgroups
Query Rules:
The text was updated successfully, but these errors were encountered: