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

Do not enable the watchdog by default

Browse Source 
Any administrative operation, performed using maxadmin or maxctrl,
that takes longer than the watchdog timeout will cause MaxScale to
be killed and restarted by the watchdog.
This commit is contained in:
Johan Wikman
2018-11-20 10:43:59 +02:00
parent 9263c1cf8d
commit e3ad827288
3 changed files with 16 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1978,3 +1978,9 @@ enabled MaxScale will check that all threads are running and notify systemd
with a "keep-alive ping". with a "keep-alive ping".
Systemd reference: https://www.freedesktop.org/software/systemd/man/systemd.service.html Systemd reference: https://www.freedesktop.org/software/systemd/man/systemd.service.html
*NOTE*: In 2.3.1 there is a deficiency that manifests itself so that if
_any_ administrative operation, performed using _maxctrl_ or _maxadmin_,
takes longer that the specified watchdog timeout, then the watchdog will
kill and restart MaxScale. Please take that into account before enabling
the watchdog.

10
Documentation/Release-Notes/MaxScale-2.3.1-Release-Notes.md
View File

@ -89,9 +89,13 @@ enabled and MaxScale will behave accordingly. Please see the
[documentation](Getting-Started/Configuration-Guide.md#systemd-watchdog) [documentation](Getting-Started/Configuration-Guide.md#systemd-watchdog)
for more details. for more details.
By default the watchdog timeout is 60 seconds. That is, if MaxScale is By default the watchdog is disabled.
hung, then systemd will detect that and restart MaxScale after slightly
more than 60 seconds. *NOTE*: In 2.3.1 there is a deficiency that manifests itself so that if
_any_ administrative operation, performed using _maxctrl_ or _maxadmin_,
takes longer that the specified watchdog timeout, then the watchdog will
kill and restart MaxScale. Please take that into account before enabling
the watchdog.
### Miscellaneous ### Miscellaneous

4
etc/maxscale.service.in
View File

@ -20,7 +20,9 @@ ExecStart=@CMAKE_INSTALL_PREFIX@/@MAXSCALE_BINDIR@/maxscale
TimeoutStartSec=120 TimeoutStartSec=120
LimitNOFILE=65535 LimitNOFILE=65535
StartLimitBurst=0 StartLimitBurst=0
WatchdogSec=60s #Please see the MaxScale release notes and/or watchdog documentation
#before turning the watchdog on.
#WatchdogSec=60s
# Only relevant when MaxScale is linked with -fsanitize=address # Only relevant when MaxScale is linked with -fsanitize=address
Environment=ASAN_OPTIONS=abort_on_error=1 Environment=ASAN_OPTIONS=abort_on_error=1