mirror of
				https://github.com/MariaDB/server.git
				synced 2025-10-31 10:56:12 +01:00 
			
		
		
		
	 946a07e8a8
			
		
	
	
	946a07e8a8
	
	
	
		
			
			Problem was that in a circular replication setup the master remembers position to events it has generated itself when reading from a slave. If there are no new events in the queue from the slave, a Gtid_list_log_event is generated to remember the last skipped event. The problem happens if there is a network delay and we generate a Gtid_list_log_event in the middle of the transaction, in which case there will be an implicit comment and a new transaction with serverid=0 will be logged. The fix was to not generate any Gtid_list_log_events in the middle of a transaction.
		
			
				
	
	
		
			30 lines
		
	
	
	
		
			527 B
		
	
	
	
		
			INI
		
	
	
	
	
	
			
		
		
	
	
			30 lines
		
	
	
	
		
			527 B
		
	
	
	
		
			INI
		
	
	
	
	
	
| !include ../my.cnf
 | |
| 
 | |
| [mysqld.1]
 | |
| gtid-domain-id=4
 | |
| server-id=4
 | |
| #
 | |
| log-slave-updates
 | |
| slave-parallel-threads=0
 | |
| gtid-strict-mode=1
 | |
| gtid-ignore-duplicates=1
 | |
| 
 | |
| #
 | |
| # Max-size row events to minimum with the idea to create
 | |
| # a number of Rows_log_event per Query.
 | |
| #
 | |
| binlog-row-event-max-size=1024
 | |
| 
 | |
| [mysqld.2]
 | |
| gtid-domain-id=2
 | |
| server-id=2
 | |
| #
 | |
| log-slave-updates
 | |
| slave-parallel-threads=0
 | |
| gtid-strict-mode=1
 | |
| gtid-ignore-duplicates=1
 | |
| binlog-row-event-max-size=1024
 | |
| # The slave will be initialized with a @@global.dbug-var value
 | |
| skip-slave-start=1
 | |
| 
 | |
| 
 |