Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
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.
Attachments
Issue Links
- relates to
-
MDEV-26 Global transaction ID
-
- Closed
-
Activity
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.
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.