[MDEV-4278] Produce a more meaningful error message on attempt to start GTID-based replication from master which does not support GTID Created: 2013-03-16  Updated: 2013-03-21  Resolved: 2013-03-21

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: replication

Issue Links:
Relates
relates to MDEV-26 Global transaction ID Closed

 Description   

If a slave was configured with GTID position, an attempt to start replication from a master which does not support GTID, e.g. from 5.5, causes the error message on start slave:

Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position; the first event '.' at 0, the last event read from 'ubuntu12-04-bin.000001' at 4, the last byte read from 'ubuntu12-04-bin.000001' at 4.'

It would be good to make it clearer more explicit, if at all possible.

 Comments   
Comment by Kristian Nielsen [ 2013-03-18 ]

Urgh, the slave doesn't attempt to detect if master knows about GTID, and if not it just sends a random junk start position. Will fix.

Comment by Kristian Nielsen [ 2013-03-21 ]

The slave now attempts to read @@global.gtid_domain_id. This fails if master
does not have GTID support, resulting in this error on the slave:

[ERROR] Slave I/O: The slave I/O thread stops because master does not support MariaDB global transaction id. A fatal error is encountered when it tries to SELECT @@GLOBAL.gtid_domain_id.

Generated at Thu Feb 08 06:55:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.