Skip to content
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

GTID in MySQL 8.4+ #4642

Open
4 tasks
renecannao opened this issue Sep 10, 2024 · 0 comments
Open
4 tasks

GTID in MySQL 8.4+ #4642

renecannao opened this issue Sep 10, 2024 · 0 comments

Comments

@renecannao
Copy link
Contributor

  • A clear description of the issue

This issue is to report an incompatibility issue with MySQL 8.4+ if GTID is used with tags.

From https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html :

A GTID is represented as a pair of coordinates, separated by a colon character (:), as shown here:
GTID = source_id:transaction_id
...
MySQL 8.4 also supports tagged GTIDs. A tagged GTID consists of three parts, separated by colon characters, as shown here:
GTID = source_id:tag:transaction_id

ProxySQL's behavior is currently undefined and needs to be investigated.

  • ProxySQL version

All the versions to the latest (2.7.0)

  • OS version

All

  • The steps to reproduce the issue

It should be enough to configure ProxySQL to process GTIDs, and on the backend enable tags in GTIDs.

Note: this affects also the binlog reader: https://github.com/sysown/proxysql_mysqlbinlog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant