Details
-
Bug
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Incomplete
-
23.02.1
-
None
Description
MaxScale error message for delayed_retry_timeout does not distinguish between read/write queries.
This was observed during SkySQL testing where the following statement was executed every 2 seconds while the primary was terminated.
SELECT * FROM sampledb.employees;
|
+----+-----------+----------+-------------------------+------+
|
| id | firstname | lastname | email | age |
|
+----+-----------+----------+-------------------------+------+
|
| 1 | john | doe | john.doe@example.com | 30 |
|
| 2 | jane | doe | jane.doe@example.com | 28 |
|
| 3 | alice | smith | alice.smith@example.com | 35 |
|
| 4 | bob | johnson | bob.johnson@example.com | 40 |
|
+----+-----------+----------+-------------------------+------+
|
We observed the write query error message while only testing reads. (IP address has been changed for privacy)
2023-06-13 12:36:47 warning: (41) [readwritesplit] [Read-Write-Service] Write query received from dbpgf14557113@192.0.2.0. 'delayed_retry_timeout' exceeded before a primary could be found. Closing client connection.
|