Skip to content

Commit ef08304

Browse files
author
Sudheesh Narayanaswamy
committed
Adding GTID Not supported to Single Server for Storage V1
1 parent 0bf336d commit ef08304

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/mysql/howto-data-in-replication.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -342,6 +342,9 @@ call mysql. az_replication_skip_gtid_transaction(‘<transaction_gtid>’)
342342
343343
The procedure can skip the transaction for the given GTID. If the GTID format is not right or the GTID transaction has already been executed, the procedure will fail to execute. The GTID for a transaction can be determined by parsing the binary log to check the transaction events. MySQL provides a utility [mysqlbinlog](https://dev.mysql.com/doc/refman/5.7/en/mysqlbinlog.html) to parse binary logs and display their contents in text format, which can be used to identify GTID of the transaction.
344344
345+
>[!Important]
346+
>This procedure can be only used to skip one transaction, and can't be used to skip gtid set or set gtid_purged.
347+
345348
To skip the next transaction after the current replication position, use the following command to identify the GTID of next transaction as shown below.
346349
347350
```sql

0 commit comments

Comments
 (0)