MXS-1367: Retry interrupted queries
The new `query_retries` parameter controls how many times an interrupted query is retried. This retrying of interrupted queries will reduce the rate of false positives that MaxScale monitors detect.
This commit is contained in:
@ -172,6 +172,15 @@ write or modify the data in the backend server. The default is 2 seconds.
|
||||
auth_write_timeout=10
|
||||
```
|
||||
|
||||
#### `query_retries`
|
||||
|
||||
The number of times an interrupted query will be retried. This feature was added
|
||||
in MaxScale 2.1.10 and is disabled by default.
|
||||
|
||||
An interrupted query is any query that is interrupted by a network
|
||||
error. Connection timeouts will not trigger a reconnection as it is advisable to
|
||||
increase the timeouts rather than to try timed out queries again.
|
||||
|
||||
#### `ms_timestamp`
|
||||
|
||||
Enable or disable the high precision timestamps in logfiles. Enabling this adds
|
||||
|
@ -22,6 +22,18 @@ release notes:
|
||||
For any problems you encounter, please consider submitting a bug report at
|
||||
[Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
### Internal Query Retries
|
||||
|
||||
The internal SQL queries that MaxScale executes to load database users as well
|
||||
as monitor the database itself can now be automatically retried if they are
|
||||
interrupted. The new global parameter, `query_retries` controls the number of
|
||||
retry attempts each query will receive if it fails due to a network problem.
|
||||
|
||||
To enable this functionality, add `query_retries=<number-of-retries>` under the
|
||||
`[maxscale]` section where _<number-of-retries>_ is a positive integer.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed in MaxScale 2.1.10.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.1.10)
|
||||
|
Reference in New Issue
Block a user