-
Notifications
You must be signed in to change notification settings - Fork 977
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
Getting: "Query Failed: Commands out of sync; you can't run this command now;" #1074
Comments
This should be fixed in 62180d7 |
Thank you for looking into this @renecannao. Unfortunately, 62180d7 did not resolve the aforementioned problem for us. We are still seeing intermittent "Commands out of sync” errors when funneling traffic through ProxySQL. |
Right this morning I came across a log where client was sending command 28 , despite ProxySQL sends that no cursor exists. Do you have a reproducible test case to help me troubleshoot this issue? Reopening this issue |
The following test script will return a "Commands out of sync" error when funneled through ProxySQL. MySQL on the other hand has no problem with it. I suspect the semicolon before the comment is somewhat relevant.
|
Thank you for the script: it allows to reproduce it.
And these the reply from mysqld to proxysql, and from proxysql to client:
So far, all looks consistent: proxysql is sending to client what received from mysqld.
What is different? |
Client capabilities when client connects to mysqld and/or proxysql: Client capabilities when proxysql connects to mysqld: There are few differences, but what really matter is that proxysql sets |
See comments in Github issue. Once applied, this change allows the user to toggle the 'client_multi_statements' flag as a global variable.
See comments in Github issue. Once applied, this change allows the user to toggle the 'client_multi_statements' flag as a global variable.
…riable Add variable client_multi_statements to address #1074
See comments in Github issue. Once applied, this change allows the user to toggle the 'client_multi_statements' flag as a global variable.
See comments in Github issue. Once applied, this change allows the user to toggle the 'client_multi_statements' flag as a global variable.
See comments in Github issue. Once applied, this change allows the user to toggle the 'client_multi_statements' flag as a global variable.
I am currently testing ProxySQL for mirroring among two slaves. As a first step, I am sending traffic only to the target slave and not the mirror. I am getting the following error in my application logs:
"Query Failed: Commands out of sync; you can't run this command now;"
The query looks like this:
SELECT
1
FROM
CJ
JOIN SJ ON SJ.id = CJ.id AND SJ.uid = xxxxxx AND SJ.time IS NULL
WHERE
CJ.another_id = yyyyyy
LIMIT 1;
Including relevant tables with configuration:
Is this abnormal behaviour? Is there a parameter that I should be looking at?
The text was updated successfully, but these errors were encountered: