proxysql

Commit Graph

Author	SHA1	Message	Date
Rene Cannao	f8c64142cb	Fix cluster CI: remove duplicate primary INSERT and add sync_algorithm=3 - Remove redundant INSERT of primary into proxysql_servers on nodes. Commit `b02147b92` added the primary to the shared PROXYSQL_SERVERS_SQL but didn't remove the pre-existing per-node INSERT, causing a UNIQUE constraint violation that broke all multi-node CI groups. - Add cluster_mysql_servers_sync_algorithm=3 to test_cluster_sync config files and update hardcoded datadir paths to match current workspace.	1 month ago
Rene Cannao	b02147b92b	Include primary in its own proxysql_servers table When a cluster node syncs proxysql_servers from the primary and runs LOAD PROXYSQL SERVERS TO RUNTIME, it rebuilds the node list from the synced data. If the primary isn't in its own proxysql_servers table, the synced list won't include it. The node then destroys the cluster monitor thread for the primary and never recreates it. Evidence: node 1 log shows "Destroyed Cluster Node Entry for host proxysql:6032" followed by "closing thread for peer proxysql:6032" after syncing proxysql_servers from the primary. After that, the node never detected any further checksum changes from the primary, causing test_cluster1-t and test_unshun_algorithm-t to fail. Fixes #5542.	1 month ago
Rene Cannao	3c4ebf0da7	Set cluster_mysql_servers_sync_algorithm=3 (auto_select) on all nodes The default value (1) syncs both configured AND runtime mysql_servers, including changes made by the monitor (read_only checks moving servers between writer/reader hostgroups). This caused circular sync: a cluster node's monitor modified servers, creating a newer epoch, and the primary synced this back — overwriting its correct config and saving the corrupted version to disk. With auto_select (3), the algorithm chooses mysql_servers_v2 when the monitor is enabled, which only syncs user-configured changes and ignores monitor-triggered runtime modifications. Evidence: node 6042's monitor removed MariaDB servers from hostgroup 1701 ("Setting status OFFLINE HARD"), creating checksum 0x7C0A67D5 with epoch 1774288555. Primary (epoch 1774288549) synced from node 6042 and saved to disk, losing hostgroup 1300 permanently. Fixes #5540.	1 month ago
Rene Cannao	a4675096b5	Fix cluster admin_variables sync: set same admin vars on primary and nodes The primary had admin-debug=false and admin-restapi_enabled=false (defaults), while cluster nodes had them set to true. Since these variables are NOT in the CLUSTER_SYNC_INTERFACES_ADMIN exclusion list, they're included in the checksum. The checksum mismatch between primary and nodes caused admin_variables sync to never converge on satellite nodes. Now the primary sets the same admin-restapi_enabled=true and admin-debug=true as all nodes, ensuring matching checksums. Fixes #5535.	1 month ago
Rene Cannao	82c112c461	Fix coverage: restore GCOV_PREFIX for primary after unsetting for cluster nodes	1 month ago
Rene Cannao	c84f4117ac	Fix pgsql admin port: set pgsql_ifaces in admin_variables, not pgsql_variables	1 month ago
Rene Cannao	98b56ec386	Move cluster node pgsql/sqlite ports to 7xxx range to avoid restapi collisions	1 month ago
Rene Cannao	48376427cf	Fix port conflicts: assign unique pgsql/sqlite ports to cluster nodes Cluster nodes only configured mysql admin and data ports, leaving pgsql (6133/6132) and sqlite (6030) at defaults — same as the primary. All nodes tried to bind the same ports, causing: 1. Bind failures for pgsql on cluster nodes 2. Cluster sync overwriting primary's pgsql config with empty tables (nodes had no working pgsql, so their pgsql tables were empty) Now each node gets unique ports for all interfaces: node N: mysql admin=6032+N10, mysql data=6033+N10, pgsql data=6133+N10, pgsql admin=6132+N10, sqlite=6030+N*10	1 month ago
Rene Cannao	35a9bfb42e	Use 'proxysql' hostname in proxysql_servers instead of 127.0.0.1 TAP tests running in the test-runner container query proxysql_servers to find cluster nodes, then connect to them directly. With 127.0.0.1, the test-runner connects to itself instead of the ProxySQL container. Using 'proxysql' (the container hostname) works from both inside the container (resolves via /etc/hosts) and from the test-runner (resolves via Docker DNS on the shared network).	1 month ago
Rene Cannao	8705685f83	Address PR review comments: port collisions, gcov, loop bounds, fastcov - RESTAPI port offset changed from 6070+i to 7070+i to avoid collision with admin/mysql ports (6072 would collide with node4 admin) - Unset GCOV_PREFIX for background cluster nodes to prevent concurrent .gcda write corruption - Cap core-node and scheduler loops to min(NUM_NODES, 3) so smaller clusters don't reference non-existent nodes - TAP_CLUSTER_NODES now respects PROXYSQL_CLUSTER_NODES and SKIP_CLUSTER_START instead of hardcoding 9 - Fix fastcov flag: -i is invalid, use --include for source filtering	1 month ago
Rene Cannao	6fcb8fd631	Run ProxySQL cluster nodes inside a single container Instead of spawning 1+9 Docker containers for the ProxySQL cluster, run all instances as background processes inside the primary container. Each node gets its own port pair (admin=6032+i10, mysql=6033+i10) and data directory. This eliminates 9 Docker containers per group, avoiding Docker networking/iptables contention that caused "no route to host" errors under parallel test execution. Changes: - start-proxysql-isolated.bash: starts cluster nodes as background processes inside the container, then initializes the cluster and installs the scheduler — all in one script - check_all_nodes.bash: polls 127.0.0.1 on different ports instead of container hostnames - env-isolated.bash: TAP_CLUSTER_NODES uses proxysql:PORT format - default/pre-proxysql.bash, legacy/pre-proxysql.bash: no longer call cluster_start.bash/cluster_init.bash (handled by start-proxysql) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	1 month ago
Rene Cannao	86e86c8ce3	Fix parallel coverage collection and improve multi-group runner - Fix code coverage race condition: Each ProxySQL instance now writes .gcda files to its own directory using GCOV_PREFIX, preventing parallel groups from overwriting each other's coverage data - Add TAP_USE_NOISE documentation for noise injection testing - Replace random stagger delay with sequential delay (STAGGER_DELAY) to guarantee proper spacing between group startups - Update README with multi-group runner, coverage, and noise injection docs	1 month ago
Rene Cannao	aa9cc7481c	Finalize infra migration and security hardening - Migrate and standardize infra-pgsql17-repl to test/infra/. - Secure all bash scripts with set -e and set -o pipefail for immediate error abort. - Implement reliable INFRA_ID preservation and propagation across all init scripts. - Restore all docker-compose.yml literals to prevent premature shell expansion. - Refactor PostgreSQL wait and post-scripts to use docker exec within isolated network. - Prevent stop-proxysql-isolated.bash from accidentally killing the test-runner container. - Update README.md with detailed instructions for all backend types and clusters. - Decouple pgsql17-repl test group from its internal infrastructure management.	2 months ago
Rene Cannao	1c62557ff2	Standardize migrated infrastructures and fix naming conventions - Restore original directory names (infra-, docker-) to ensure DNS resolution compatibility. - Implement robust relative path derivation for WORKSPACE and REPO_ROOT. - Add SUDO and diag helpers for containerized environment portability. - Mount Docker socket and binary in test-runner for DooD support. - Redirect legacy script calls in test hooks to local infra control paths. - Remove obsolete test/cluster/check_all_nodes.bash.	2 months ago

14 Commits (dca01d4eaf32c8363ff14fb4f74a46deb73e11c3)