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

Use a known binlog name for Galera

Browse Source 
The binlog files for Galera shouldn't rely on implicit naming simply due
to the fact that it logs a warning.
This commit is contained in:
Markus Mäkelä 2019-04-17 13:31:36 +03:00
parent 163b3a2da5
commit d77530a2a4
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
maxscale-system-test/mdbci/cnf/galera_server1.cnf
View File

@ -7,7 +7,7 @@ wsrep_on=ON
# Row binary log format is required by Galera
binlog_format=ROW
log-bin
log-bin=mar-bin
# InnoDB is currently the only storage engine supported by Galera
default-storage-engine=innodb

2
maxscale-system-test/mdbci/cnf/galera_server2.cnf
View File

@ -7,7 +7,7 @@ wsrep_on=ON
# Row binary log format is required by Galera
binlog_format=ROW
log-bin
log-bin=mar-bin
# InnoDB is currently the only storage engine supported by Galera
default-storage-engine=innodb

2
maxscale-system-test/mdbci/cnf/galera_server3.cnf
View File

@ -7,7 +7,7 @@ wsrep_on=ON
# Row binary log format is required by Galera
binlog_format=ROW
log-bin
log-bin=mar-bin
# InnoDB is currently the only storage engine supported by Galera
default-storage-engine=innodb

2
maxscale-system-test/mdbci/cnf/galera_server4.cnf
View File

@ -7,7 +7,7 @@ wsrep_on=ON
# Row binary log format is required by Galera
binlog_format=ROW
log-bin
log-bin=mar-bin
# InnoDB is currently the only storage engine supported by Galera
default-storage-engine=innodb