2/21/2023 0 Comments Bobok siang dengan![]() ![]() The last thing to do is of course to resync the slave. There is a specific statement for the first part: mysql> start slave until sql_after_mts_gaps Īnd now I can finally skip the error and restart replication: So the solution to my problem is first to make sure that there is no execution gap, and only then to skip the offendingĮvent. Because the current implementation allows execution of transactions on different databases in a different order on the slave than on the master, this is not necessarily the position of the most recently executed transaction. When using a multi-threaded slave (by setting slave_parallel_workers to a nonzero value in MySQLĥ.6.3 and later), the value in this column actually represents a “low-water” mark, before which no uncommitted transactions remain. ![]() Quoting the documentation about Exec_Master_Log_Pos: ![]() The issue is that the positions reported by SHOW SLAVE STATUS are misleading when using MTS. Note that the position reported with Exec_Master_Log_Pos has moved forward, but I still have my duplicate key error. Mysql> set global sql_slave_skip_counter=1 Inemuri, Seni Tidur Masyarakat Jepang.Last_SQL_Error: Worker 0 failed executing transaction '' at master log mysql-bin.000017, end_log_pos 1216451 Error 'Duplicate entry '1001' for key 'PRIMARY'' on query.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |