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

MXS-2090 Update documentation

Browse Source
This commit is contained in:
Johan Wikman
2018-10-16 22:12:48 +03:00
parent 0e2e74d1e1
commit 8d60bd04d2
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/Routers/Binlogrouter.md
View File

@ -380,8 +380,8 @@ encryption_key_file=/var/binlogs/enc_key.txt
From MaxScale 2.3 onwards it is possible to specify secondary masters that From MaxScale 2.3 onwards it is possible to specify secondary masters that
the binlog router can use in case the connection to the default master fails. the binlog router can use in case the connection to the default master fails.
**Note:** This is _only_ supported for gtid based replication in conjunction **Note:** This is _only_ supported in conjunction with a Galera cluster and
with a Galera cluster and provided the following holds: provided the following holds:
* `@@log_slave_updates` is enabled on all servers, * `@@log_slave_updates` is enabled on all servers,
* all nodes in the Galera cluster have the *same* `server_id`, and * all nodes in the Galera cluster have the *same* `server_id`, and
* all nodes in the Galera cluster use the *same* basename for the * all nodes in the Galera cluster use the *same* basename for the