proxysql

History

Rene Cannao 53a6f011d2 Fix infra-mysql57-binlog infrastructure for GTID binlog reader tests This commit fixes the infra-mysql57-binlog infrastructure to properly support GTID-based query routing using proxysql_mysqlbinlog reader containers. The infrastructure was migrated from the old CI to the new isolated CI structure. PROBLEM: The binlog tests (test_binlog_reader-t, etc.) were failing because: 1. ProxySQL could not connect to the proxysql_mysqlbinlog readers on port 6020 2. The mysql_servers table had gtid_port pointing to MySQL containers instead of the reader containers 3. Hostname resolution was broken - mysql1.${INFRA} resolved to MySQL containers for queries but also needed to resolve to reader containers for GTID tracking SOLUTION: 1. docker-compose.yml - Added Docker network aliases to reader services: - reader1 service now has alias 'mysql1.${INFRA}' - reader2 service now has alias 'mysql2.${INFRA}' - reader3 service now has alias 'mysql3.${INFRA}' This allows ProxySQL to connect to mysql1.${INFRA}:3306 for queries (MySQL) and mysql1.${INFRA}:6020 for GTID tracking (reader), using the same hostname but different ports resolved to different containers via Docker networking. 2. conf/proxysql/infra-config.sql - Fixed GTID configuration: - Set gtid_port=6020 for all mysql_servers (was incorrectly set before) - Added comments explaining the GTID reader architecture - Added 'root' user to mysql_users for mysqlbinlog tests that connect as root - Users: sbtest7, sbtest8, root (for binlog dump tests) 3. .env - Fixed default INFRA value: - Changed from INFRA=${INFRA:-.} to INFRA=${INFRA:-infra-mysql57-binlog} - This ensures proper hostname generation like 'mysql1.infra-mysql57-binlog' - The old value '.' created invalid hostnames like 'mysql1..' ARCHITECTURE: - MySQL containers (mysql1, mysql2, mysql3): Handle queries on port 3306 - Reader containers (reader1, reader2, reader3): Run proxysql_mysqlbinlog, connect to their respective MySQL instances, and expose GTID info on port 6020 - Network aliases allow same hostname (mysql1.${INFRA}) to resolve to different containers based on port: 3306→MySQL, 6020→reader TESTS AFFECTED: - test_binlog_reader-t (PASSED) - test_binlog_reader_uses_previous_hostgroup-t - test_com_binlog_dump_enables_fast_forward-t - test_binlog_fast_forward-t Related: legacy-binlog TAP group uses this infrastructure	1 month ago
..
infra-config.sql	Fix infra-mysql57-binlog infrastructure for GTID binlog reader tests	1 month ago

Rene Cannao 53a6f011d2 Fix infra-mysql57-binlog infrastructure for GTID binlog reader tests

This commit fixes the infra-mysql57-binlog infrastructure to properly support
GTID-based query routing using proxysql_mysqlbinlog reader containers. The
infrastructure was migrated from the old CI to the new isolated CI structure.

PROBLEM:
The binlog tests (test_binlog_reader-t, etc.) were failing because:
1. ProxySQL could not connect to the proxysql_mysqlbinlog readers on port 6020
2. The mysql_servers table had gtid_port pointing to MySQL containers instead of
   the reader containers
3. Hostname resolution was broken - mysql1.${INFRA} resolved to MySQL containers
   for queries but also needed to resolve to reader containers for GTID tracking

SOLUTION:

1. docker-compose.yml - Added Docker network aliases to reader services:
   - reader1 service now has alias 'mysql1.${INFRA}'
   - reader2 service now has alias 'mysql2.${INFRA}'
   - reader3 service now has alias 'mysql3.${INFRA}'

   This allows ProxySQL to connect to mysql1.${INFRA}:3306 for queries (MySQL)
   and mysql1.${INFRA}:6020 for GTID tracking (reader), using the same hostname
   but different ports resolved to different containers via Docker networking.

2. conf/proxysql/infra-config.sql - Fixed GTID configuration:
   - Set gtid_port=6020 for all mysql_servers (was incorrectly set before)
   - Added comments explaining the GTID reader architecture
   - Added 'root' user to mysql_users for mysqlbinlog tests that connect as root
   - Users: sbtest7, sbtest8, root (for binlog dump tests)

3. .env - Fixed default INFRA value:
   - Changed from INFRA=${INFRA:-.} to INFRA=${INFRA:-infra-mysql57-binlog}
   - This ensures proper hostname generation like 'mysql1.infra-mysql57-binlog'
   - The old value '.' created invalid hostnames like 'mysql1..'

ARCHITECTURE:
- MySQL containers (mysql1, mysql2, mysql3): Handle queries on port 3306
- Reader containers (reader1, reader2, reader3): Run proxysql_mysqlbinlog,
  connect to their respective MySQL instances, and expose GTID info on port 6020
- Network aliases allow same hostname (mysql1.${INFRA}) to resolve to different
  containers based on port: 3306→MySQL, 6020→reader

TESTS AFFECTED:
- test_binlog_reader-t (PASSED)
- test_binlog_reader_uses_previous_hostgroup-t
- test_com_binlog_dump_enables_fast_forward-t
- test_binlog_fast_forward-t

Related: legacy-binlog TAP group uses this infrastructure

infra-config.sql

Fix infra-mysql57-binlog infrastructure for GTID binlog reader tests