mysql配置文件中跳过1032_MySQL 1032和1062跳过错误总结

最新推荐文章于 2023-08-15 11:43:31 发布

solomonhume

最新推荐文章于 2023-08-15 11:43:31 发布

阅读量763

点赞数

文章标签： mysql配置文件中跳过1032

本文链接：https://blog.csdn.net/weixin_34236672/article/details/113655409

版权

本文总结了MySQL在配置文件中处理1032和1062错误的方法，包括slave_exec_mode的IDEMPOTENT和STRICT模式，以及sql_slave_skip_counter参数的影响。在不同binlog_format下，错误处理方式不同，如ROW格式会跳过整个事务，而STATEMENT格式则可能跳过单个错误SQL。slave_skip_errors参数允许跳过特定错误，但需注意其对事务处理的影响。GTID复制时，可通过gtid_next设置来处理错误。

摘要由CSDN通过智能技术生成

MySQL跳过 1032 1062错误

传统复制情况

slave_exec_mode(global级别) IDEMPOTENT or STRICT

Controls how a slave thread resolves conflicts and errors during replication. IDEMPOTENT mode causes suppression of duplicate-key and no- key-found errors; STRICT means no such suppression takes place.

IDEMPOTENT mode is intended for use in multi-master replication, circular replication, and some other special replication scenarios for NDB Cluster Replication. (See Section 21.6.10, “NDB Cluster Replication: Multi-Master and Circular Replication”, and Section 21.6.11, “NDB Cluster Replication Conflict Resolution”, for more information.) NDB Cluster ignores any value explicitly set for slave_exec_mode, and always treats it as IDEMPOTENT.

In MySQL Server 5.7, STRICT mode is the default value.

or storage engines other than NDB, IDEMPOTENT mode should be used only when you are absolutely sure that duplicate-key errors and key-not-