Delayed Retrying of Failed Queries with MaxScale's Read/Write Split Router
Overview
The Read/Write Split Router (readwritesplit) routes write queries to the primary server and load balances read-only queries between one or more replica servers. If a server fails, then the router may need to retry failed queries on a different server. The retry may need to be delayed in some cases, such as when automatic failover is in progress.
Configuring Delayed Retries for Failed Queries
1. Configure delayed retries for failed queries by configuring several parameters for the Read/Write Split Router in maxscale.cnf.
| Parameter | Description |
|---|---|
| delayed_retry | • When this parameter is enabled, failed queries will not immediately return an error to the client. Instead, the router will retry the query if a different server becomes available before the timeout is reached. • This parameter is disabled by default. |
| delayed_retry_timeout | • The maximum amount of time to wait until returning an error if a query fails. • The value can be followed by any of the following units: h, m, s, and ms, for specifying durations in hours, minutes, seconds, and milliseconds. • The default value is 10 seconds. |
For example:
[split-router] type = service router = readwritesplit ... delayed_retry = true delayed_retry_timeout = 30s
2. Restart the MaxScale instance.
$ sudo systemctl restart maxscale
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
