It also makes sense to fix the opposite case: skip non-GTID coordinates when GTID mode is enabled. It is important for multi-threaded slaves, because GTID is the only reliable slave state source for MTS.
I had plans to implement that for the next release. Let's keep this report to fix both GTID and non-GTID cases.
It also makes sense to fix the opposite case: skip non-GTID coordinates when GTID mode is enabled. It is important for multi-threaded slaves, because GTID is the only reliable slave state source for MTS.
I had plans to implement that for the next release. Let's keep this report to fix both GTID and non-GTID cases.