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

MXS-3132: Fix monitor timeouts default values

Browse Source 
The values are now what the documentation states they are.
This commit is contained in:
Markus Mäkelä
2020-08-27 08:20:16 +03:00
parent 23e0df314f
commit dbe94e2dbe
2 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
Documentation/Monitors/Monitor-Common.md
View File

@ -27,8 +27,7 @@ should be queried more often. The smallest possible value is 100. If querying
the servers takes longer than `monitor_interval`, the effective update rate is the servers takes longer than `monitor_interval`, the effective update rate is
reduced. reduced.
The default value of `monitor_interval` was updated from 10000 milliseconds to The default value of `monitor_interval` is 2000 milliseconds.
2000 milliseconds in MaxScale 2.2.0.
``` ```
monitor_interval=2500 monitor_interval=2500
@ -41,7 +40,7 @@ in seconds and the minimum value is 1 second. The default value for this
parameter is 3 seconds. parameter is 3 seconds.
``` ```
backend_connect_timeout=6 backend_connect_timeout=3
``` ```
### `backend_write_timeout` ### `backend_write_timeout`
@ -51,7 +50,7 @@ seconds and the minimum value is 1 second. The default value for this parameter
is 3 seconds. is 3 seconds.
``` ```
backend_write_timeout=4 backend_write_timeout=3
``` ```
### `backend_read_timeout` ### `backend_read_timeout`
@ -61,7 +60,7 @@ in seconds and the minimum value is 1 second. The default value for this
parameter is 3 seconds. parameter is 3 seconds.
``` ```
backend_read_timeout=2 backend_read_timeout=3
``` ```
### `backend_connect_attempts` ### `backend_connect_attempts`
@ -72,7 +71,7 @@ monitoring loop. The default is 1. Every attempt may take up to
successful, the backend is considered to be unreachable and down. successful, the backend is considered to be unreachable and down.
``` ```
backend_connect_attempts=3 backend_connect_attempts=1
``` ```
### `disk_space_threshold` ### `disk_space_threshold`

4
server/core/config.cc
View File

@ -361,8 +361,8 @@ const MXS_MODULE_PARAM config_monitor_params[] =
{CN_SERVERS, MXS_MODULE_PARAM_STRING}, {CN_SERVERS, MXS_MODULE_PARAM_STRING},
{CN_MONITOR_INTERVAL, MXS_MODULE_PARAM_COUNT, "2000"}, {CN_MONITOR_INTERVAL, MXS_MODULE_PARAM_COUNT, "2000"},
{CN_BACKEND_CONNECT_TIMEOUT, MXS_MODULE_PARAM_COUNT, "3"}, {CN_BACKEND_CONNECT_TIMEOUT, MXS_MODULE_PARAM_COUNT, "3"},
{CN_BACKEND_READ_TIMEOUT, MXS_MODULE_PARAM_COUNT, "1"}, {CN_BACKEND_READ_TIMEOUT, MXS_MODULE_PARAM_COUNT, "3"},
{CN_BACKEND_WRITE_TIMEOUT, MXS_MODULE_PARAM_COUNT, "2"}, {CN_BACKEND_WRITE_TIMEOUT, MXS_MODULE_PARAM_COUNT, "3"},
{CN_BACKEND_CONNECT_ATTEMPTS, MXS_MODULE_PARAM_COUNT, "1"}, {CN_BACKEND_CONNECT_ATTEMPTS, MXS_MODULE_PARAM_COUNT, "1"},
{CN_JOURNAL_MAX_AGE, MXS_MODULE_PARAM_COUNT, "28800"}, {CN_JOURNAL_MAX_AGE, MXS_MODULE_PARAM_COUNT, "28800"},