You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
starting from version 2.0.9 when using proyxsql-binlog-reader for causal reads, Queries_GTID_sync field in stats_mysql_connection_pool table is always 0.
Queries_GTID_sync will be always 0, although all queries will be routed correctly
The text was updated successfully, but these errors were encountered:
MaxFedotov
changed the title
proxysql 2.10 empty Queries_GTID_sync field in stats_mysql_connection_pool
proxysql 2.0.10 empty Queries_GTID_sync field in stats_mysql_connection_pool
Mar 25, 2020
MaxFedotov
changed the title
proxysql 2.0.10 empty Queries_GTID_sync field in stats_mysql_connection_pool
proxysql 2.0.10 empty Queries_GTID_sync field in stats_mysql_connection_pool table
Mar 25, 2020
Hi @MaxFedotov .
Thank you for the report.
We identified the root cause:
PR #2469 broke this, as it stops setting with_gtid , later required in MySQL_Connection::handler() to increment parent->queries_gtid_sync.
Hello,
starting from version 2.0.9 when using proyxsql-binlog-reader for causal reads, Queries_GTID_sync field in stats_mysql_connection_pool table is always 0.
How to reproduce:
Install proxysql version 2.0.9 or 2.0.10
build proxysql-binlog-reader, configure proxysql and use test from this article: https://www.percona.com/blog/2020/02/18/configuring-proxysql-binlog-reader/
run test and select data from stats_mysql_connection_pool table
Queries_GTID_sync will be always 0, although all queries will be routed correctly
The text was updated successfully, but these errors were encountered: