-
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
when mariadb global autocommit is OFF, query though proxysql will block forever after a "set autocommit=0;" #873
Comments
@MOON-CLJ : thank you for the report. I am not able to reproduce this behavior in the systems I am using. Although they are all MySQL and Percona sandboxes, I do not think that the fact you are using MariaDB is relevant.
Finally, could you attach the file resulting from this command executed on 192.168.31.100:
Thanks |
@MOON-CLJ : I managed to reproduce it. The important bit to reproduce it is:
Investigating. |
confirm "seems like proxysql try 'set autocommit=0' again and again" from mariadb's general_log, a lot of
we use docker, so we use './proxysql -f -D /data/proxysql -c /etc/proxysql.cnf',
|
@renecannao okay, thx。 |
This seems a side effect of a MySQL bug |
This is related to a MySQL server bug that makes ProxySQL believe that |
@renecannao thx for the investigation。 |
Conflicts: include/mysql_connection.h
Created workaround in v1.3.3 and v1.4.0 |
proxysql version: use source from https://github.com/sysown/proxysql/archive/v1.3.2-1.tar.gz, compile use just "make"
mariadb version:
proxysql conf:
any statement after "set autocommit=0;" will block forever。
during the blocking there is more info from maraidb's information_schema.processlist, the proccess which id is 263841 come from the proxysql。seems like proxysql try "set autocommit=0" again and again, as you can see QUERY_ID's change and INFO's change during the blocking。
pls check it, thx in advance!
The text was updated successfully, but these errors were encountered: