I have been struggling with keeping replication working. This is what happened before (also my topic): mysql 5.6 gtid replication slave stuck (system lock)?
on top of this getting into system lock within hours all the time, I have tweaked both server's setting before I dumped the server again to rebuild the slave from scratch (again, 3rd time in 2 days), now I let the slave process a bit, then after "stop slave" I restarted mysql on the master, and issued "start slave", just to get the famous 1236 error again. GTID settings were never changed, it has been on ever since I installed the server to begin with days ago.
(Got fatal error 1236 from master when reading data from binary log: 'Found old binary log without GTIDs while looking for the oldest binary log that contains any GTID that is not in the given gtid set')
Does anyone have any idea what could be causing this?
Also, I don't know if it is normal or not, but I find it strange that:
mysql> SHOW VARIABLES LIKE '%gtid%'; +---------------------------------+-----------+ | Variable_name | Value | +---------------------------------+-----------+ | binlog_gtid_simple_recovery | OFF | | enforce_gtid_consistency | ON | | gtid_executed | | | gtid_mode | ON | | gtid_next | AUTOMATIC | | gtid_owned | | | gtid_purged | | | simplified_binlog_gtid_recovery | OFF | +---------------------------------+-----------+ 8 rows in set (0.00 sec)
Is it normal that gtid_executed is empty on the master? (Is it just a slave value?)
Would it help to just "reset master" to get rid of all the binlogs and then rebuild the slave from a fresh backup (again... 4th time in 2 days) ?
Btw the original problem still stands (that's in the other topic), but because I am not even there to solve that one ....
Regards