mirror of
https://github.com/MariaDB/server.git
synced 2025-10-31 19:06:14 +01:00
b89de2b2ce
The --gtid-ignore-duplicates option was not working correctly with row-based replication. When a row event was completed, but before committing, there was a small window where another multi-source SQL thread could wrongly try to re-execute the same transaction, without properly ignoring the duplicate GTID. This would lead to duplicate key error or out-of-order GTID error or similar. Thanks to Matt Neth for reporting this and giving an easy way to reproduce the issue.
28 lines
395 B
INI
28 lines
395 B
INI
!include my.cnf
|
|
|
|
[mysqld.1]
|
|
log-slave-updates
|
|
loose-innodb
|
|
binlog-format=mixed
|
|
|
|
[mysqld.2]
|
|
log-slave-updates
|
|
loose-innodb
|
|
binlog-format=mixed
|
|
|
|
[mysqld.3]
|
|
log-bin=server3-bin
|
|
log-slave-updates
|
|
loose-innodb
|
|
binlog-format=mixed
|
|
|
|
[mysqld.4]
|
|
server-id=4
|
|
log-bin=server4-bin
|
|
log-slave-updates
|
|
loose-innodb
|
|
binlog-format=mixed
|
|
|
|
[ENV]
|
|
SERVER_MYPORT_4= @mysqld.4.port
|
|
SERVER_MYSOCK_4= @mysqld.4.socket
|