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

MariaDB Monitor documentation: clarify replication_password encryption

Browse Source
This commit is contained in:
Esa Korhonen
2018-01-04 16:51:24 +02:00
parent e5d9ca4af8
commit ad9b29600f
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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 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 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 ### Configuration parameters
@ -330,6 +330,10 @@ user.
The credentials used for replication must have the `REPLICATION SLAVE` The credentials used for replication must have the `REPLICATION SLAVE`
privilege. 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` #### `failover_timeout`
Time limit for the cluster failover in seconds. The default value is 90 Time limit for the cluster failover in seconds. The default value is 90