hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document retry_on_failure behavior

Browse Source 
The feature does not work in 2.4 and should be documented as a
non-functional parameter that will be removed in the future.
This commit is contained in:
Markus Mäkelä
2019-12-31 07:54:46 +02:00
parent 2c2363c639
commit 08fc4b9146
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/Getting-Started/Configuration-Guide.md
View File

@ -1487,6 +1487,11 @@ this might cause conflicts when MariaDB MaxScale tries to authenticate users.
### `retry_on_failure` ### `retry_on_failure`
**Note:** This feature is ignored by MaxScale 2.4 and will be removed in future
versions. This is due to the fact that a failure to bind to a network
interface is a serious error which should always be investigated and is not
related to network outages.
The retry_on_failure parameter controls whether MariaDB MaxScale will try to The retry_on_failure parameter controls whether MariaDB MaxScale will try to
restart failed services and accepts a boolean value. This functionality is restart failed services and accepts a boolean value. This functionality is
enabled by default to prevent services being permanently disabled if the enabled by default to prevent services being permanently disabled if the
@ -1546,6 +1551,9 @@ max_connections=100
### `max_retry_interval` ### `max_retry_interval`
**Note:** This feature has been removed from MaxScale 2.4. See
[`retry_on_failure`](#retry_on_failure) for more details.
Configure the maximum interval between consecutive attempts to bind to an Configure the maximum interval between consecutive attempts to bind to an
interface. The default value for this parameter is 3600 seconds. This interface. The default value for this parameter is 3600 seconds. This
parameter was introduced in MaxScale 2.2.0. parameter was introduced in MaxScale 2.2.0.