Andrei Elkin 946a07e8a8 Fix for MDEV-9670 server_id mysteriously set to 0 ...

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.

2017-07-02 19:47:30 +03:00

3.1 KiB

Raw Blame History

View Raw