Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
6.1.1
-
None
-
maxscale version 6.1.1
server protocol - MariaDBBackend
monitor module - mariadbmon
service router - readwritesplit
retry_failed_reads = false
delayed_retry = false
transaction_replay = false
listener protocol - MariaDBClient
backend servers - mariadb in docker
Server version: 5.5.5-10.5.12-MariaDB-1:10.5.12+maria~focal-log mariadb.org binary distributionmaxscale version 6.1.1 server protocol - MariaDBBackend monitor module - mariadbmon service router - readwritesplit retry_failed_reads = false delayed_retry = false transaction_replay = false listener protocol - MariaDBClient backend servers - mariadb in docker Server version: 5.5.5-10.5.12-MariaDB-1:10.5.12+maria~focal-log mariadb.org binary distribution
Description
How to reproduce
1. run long running query:
MariaDB [zabbix]> select count(1) from history; |
2. restart mariadb server query running on
service mysql-zabbix restart
|
Actual behaviour
Query hangs forever in client.
Expected behaviour
I think client should receive error (when retry_failed_reads=false) or maxscale retry query on live server (when retry_failed_reads=true). Is it correct or I missed something in documentation ?