GTID 的副本服务器。这可以通过在 CHANGE REPLICATION SOURCE 命令中使用参数 ASSIGN_GTIDS_TO_ANONYMOUS...
in the binlog event i can see | SET @@SESSION.GTID_NEXT= 'ANONYMOUS' this info if this event came to slave server exec_masterlog position is get stuck it cant moving in slave replication .. after giving sql slave skip counter=1 .. than only its moving ... else second behind master...
Error 1782: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON → Comments Comments loading... Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions...
← Error 1782: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON ↑ MariaDB Error Codes 1700 to 1799 ↑ Error 1784: Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF → Comments Comments loading... Content reproduced on...