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

MXS-2797: Fix handle_events documentation

Browse Source 
The parameter was called handle_server_events when in reality it was
handle_events.
This commit is contained in:
Markus Mäkelä
2019-12-17 13:21:11 +02:00
parent b0a1eddb6c
commit b3f44adb16
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/Monitors/MariaDB-Monitor.md
View File

@ -35,7 +35,7 @@ Table of Contents
* [verify_master_failure and master_failure_timeout](#verify_master_failure-and-master_failure_timeout) * [verify_master_failure and master_failure_timeout](#verify_master_failure-and-master_failure_timeout)
* [servers_no_promotion](#servers_no_promotion) * [servers_no_promotion](#servers_no_promotion)
* [promotion_sql_file and demotion_sql_file](#promotion_sql_file-and-demotion_sql_file) * [promotion_sql_file and demotion_sql_file](#promotion_sql_file-and-demotion_sql_file)
* [handle_server_events](#handle_server_events) * [handle_events](#handle_events)
* [Troubleshooting](#troubleshooting) * [Troubleshooting](#troubleshooting)
* [Failover/switchover fails](#failoverswitchover-fails) * [Failover/switchover fails](#failoverswitchover-fails)
* [Slave detection shows external masters](#slave-detection-shows-external-masters) * [Slave detection shows external masters](#slave-detection-shows-external-masters)
@ -327,7 +327,7 @@ being demoted or promoted by cluster manipulation commands. See the sections on
`promotion_sql_file` and `demotion_sql_file` for more information. `promotion_sql_file` and `demotion_sql_file` for more information.
The monitor can manipulate scheduled server events when promoting or demoting a The monitor can manipulate scheduled server events when promoting or demoting a
server. See the section on `handle_server_events` for more information. server. See the section on `handle_events` for more information.
All cluster operations can be activated manually through MaxAdmin/MaxCtrl. See All cluster operations can be activated manually through MaxAdmin/MaxCtrl. See
section [Manual activation](#manual-activation) for more details. section [Manual activation](#manual-activation) for more details.
@ -782,7 +782,7 @@ slave threads are stopped, breaking replication.
promotion_sql_file=/home/root/scripts/promotion.sql promotion_sql_file=/home/root/scripts/promotion.sql
demotion_sql_file=/home/root/scripts/demotion.sql demotion_sql_file=/home/root/scripts/demotion.sql
``` ```
#### `handle_server_events` #### `handle_events`
This setting is on by default. If enabled, the monitor continuously queries the This setting is on by default. If enabled, the monitor continuously queries the
servers for enabled scheduled events and uses this information when performing servers for enabled scheduled events and uses this information when performing

2
Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md
View File

@ -133,7 +133,7 @@ not.
Server events lauched by the event scheduler thread are now handled during Server events lauched by the event scheduler thread are now handled during
cluster modification operations. See cluster modification operations. See
[handle_server_events](../Monitors/MariaDB-Monitor.md#handle_server_events) [handle_events](../Monitors/MariaDB-Monitor.md#handle_events)
for more information. for more information.
#### Unused parameters #### Unused parameters