proxysql

Author SHA1 Message Date

Author	SHA1	Message	Date
Rene Cannao	fe91e290d8	test(mysqlx): add behavioural-validation and stress harnesses Three companion harnesses for the post-merge confidence work tracked in issues #5677 (smoke + soak), #5678 (behavioural validation), and #5681 (stress test). These are NOT TAP unit tests — they require live infrastructure (a real MySQL 8.x and a running ProxySQL with the mysqlx plugin loaded). They post-date the merge window and exist to let an operator with a staging environment reproduce the validation. * test/scripts/mysqlx/README.md — setup recipe (ProxySQL admin config, MySQL backend bring-up via docker or dbdeployer, the invocation lines for both harnesses). * test/scripts/mysqlx/behavioral_validation.py — exercises two scenarios from issue #5678. Scenario 1 ("SIGTERM mid-traffic") opens N X-Protocol clients running steady SELECT loops, sends SIGTERM to proxysql, then verifies each client received a clean Mysqlx::Error frame with code 1053 ("Server is shutting down") rather than an unannounced TCP RST. Exercises MysqlxSession::shutdown_notify_client (commit `55e90d1a7`). Scenario 2 ("LOAD MYSQLX ROUTES TO RUNTIME mid-traffic") opens clients on route 'r1', drops r1 from admin and reloads, then verifies in-flight sessions continue while a new connection to the removed route is refused — the documented remove_listener_for_route semantics. * test/scripts/mysqlx/stress.py — opens N concurrent X-Protocol clients (target N=1000), drives churn, captures throughput, error rate, RSS, fd count, thread count, and stats_mysqlx_routes over time. Pass criteria from issue #5681: 60-min run with no crash, no monotonic memory/fd growth, error rate < 0.1%. Writes a metrics CSV for plotting. Both Python scripts use mysql-connector-python's mysqlx module (X DevAPI bindings) for the data-plane connection and the classic mysql.connector module for admin-port operations. These are scaffolds — runnable but not yet exercised against real infrastructure. Confidence gain comes from someone running them on staging and posting results to the linked issues.	2 months ago

Rene Cannao

test(mysqlx): add behavioural-validation and stress harnesses

Three companion harnesses for the post-merge confidence work tracked
in issues #5677 (smoke + soak), #5678 (behavioural validation), and
#5681 (stress test). These are NOT TAP unit tests — they require live
infrastructure (a real MySQL 8.x and a running ProxySQL with the
mysqlx plugin loaded). They post-date the merge window and exist to
let an operator with a staging environment reproduce the validation.

* test/scripts/mysqlx/README.md — setup recipe (ProxySQL admin
  config, MySQL backend bring-up via docker or dbdeployer, the
  invocation lines for both harnesses).

* test/scripts/mysqlx/behavioral_validation.py — exercises two
  scenarios from issue #5678. Scenario 1 ("SIGTERM mid-traffic")
  opens N X-Protocol clients running steady SELECT loops, sends
  SIGTERM to proxysql, then verifies each client received a clean
  Mysqlx::Error frame with code 1053 ("Server is shutting down")
  rather than an unannounced TCP RST. Exercises
  MysqlxSession::shutdown_notify_client (commit 55e90d1a7).
  Scenario 2 ("LOAD MYSQLX ROUTES TO RUNTIME mid-traffic") opens
  clients on route 'r1', drops r1 from admin and reloads, then
  verifies in-flight sessions continue while a new connection to the
  removed route is refused — the documented
  remove_listener_for_route semantics.

* test/scripts/mysqlx/stress.py — opens N concurrent X-Protocol
  clients (target N=1000), drives churn, captures throughput, error
  rate, RSS, fd count, thread count, and stats_mysqlx_routes over
  time. Pass criteria from issue #5681: 60-min run with no crash, no
  monotonic memory/fd growth, error rate < 0.1%. Writes a metrics CSV
  for plotting.

Both Python scripts use mysql-connector-python's mysqlx module (X
DevAPI bindings) for the data-plane connection and the classic
mysql.connector module for admin-port operations.

These are scaffolds — runnable but not yet exercised against real
infrastructure. Confidence gain comes from someone running them on
staging and posting results to the linked issues.

1 Commits (feature/pgsql-native-backend-protocol)