Clarify query_retries documentation
The parameter documentation did not clearly specify that it affects only internal queries done by the core and monitors.
This commit is contained in:
@ -174,13 +174,14 @@ auth_write_timeout=10
|
|||||||
|
|
||||||
#### `query_retries`
|
#### `query_retries`
|
||||||
|
|
||||||
The number of times an interrupted query will be retried. This feature was added
|
The number of times an interrupted internal query will be retried. This feature
|
||||||
in MaxScale 2.1.10 and is disabled by default.
|
was added in MaxScale 2.1.10 and is disabled by default.
|
||||||
|
|
||||||
An interrupted query is any query that is interrupted by a network
|
An interrupted query is any query that is interrupted by a network
|
||||||
error. Connection timeouts are included in network errors and thus is it
|
error. Connection timeouts are included in network errors and thus is it
|
||||||
advisable to make sure that the value of `query_retry_timeout` is set to an
|
advisable to make sure that the value of `query_retry_timeout` is set to an
|
||||||
adequate value.
|
adequate value. Internal queries are only used to retrieve authentication data
|
||||||
|
and monitor the servers.
|
||||||
|
|
||||||
#### `query_retry_timeout`
|
#### `query_retry_timeout`
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user