diff --git a/Documentation/Monitors/MariaDB-Monitor.md b/Documentation/Monitors/MariaDB-Monitor.md index 87c2f329b..aa86d1cd4 100644 --- a/Documentation/Monitors/MariaDB-Monitor.md +++ b/Documentation/Monitors/MariaDB-Monitor.md @@ -35,7 +35,7 @@ Table of Contents * [verify_master_failure and master_failure_timeout](#verify_master_failure-and-master_failure_timeout) * [servers_no_promotion](#servers_no_promotion) * [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) * [Failover/switchover fails](#failoverswitchover-fails) * [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. 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 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 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 servers for enabled scheduled events and uses this information when performing diff --git a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md index e1d452bc9..a4915a181 100644 --- a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md @@ -133,7 +133,7 @@ not. Server events lauched by the event scheduler thread are now handled during 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. #### Unused parameters