From ad9b29600f53291395c1deac003c24b4304adf2b Mon Sep 17 00:00:00 2001 From: Esa Korhonen Date: Thu, 4 Jan 2018 16:51:24 +0200 Subject: [PATCH] MariaDB Monitor documentation: clarify replication_password encryption --- Documentation/Monitors/MariaDB-Monitor.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Documentation/Monitors/MariaDB-Monitor.md b/Documentation/Monitors/MariaDB-Monitor.md index 32412f53a..e0cc8134d 100644 --- a/Documentation/Monitors/MariaDB-Monitor.md +++ b/Documentation/Monitors/MariaDB-Monitor.md @@ -275,7 +275,7 @@ seconds (faster than `backend_read_timeout` and `backend_write_timeout`). The backends must all use GTID-based replication, and the domain id should not change during a switchover or failover. Master and slaves must have -well-behaving GTIDs: no extra events on slave servers. +well-behaving GTIDs with no extra events on slave servers. ### Configuration parameters @@ -330,6 +330,10 @@ user. The credentials used for replication must have the `REPLICATION SLAVE` privilege. +`replication_password` uses the same encryption scheme as other password +parameters. If password encryption is in use, `replication_password` must be +encrypted with the same key to avoid erroneous decryption. + #### `failover_timeout` Time limit for the cluster failover in seconds. The default value is 90