Repair MySQL 5.6 GTID replication by injecting empty transactions
Since SQL_SLAVE_SKIP_COUNTER doesn’t work with GTID we need to find a way to ignore that transaction. The way to do it is creating a new empty transaction with it the GTID we want to skip.
After the START SLAVE the slave checks that transaction 5 is already in its own binary log and that means that it has been executed.
This is an easy way to skip some transactions but take in account that by doing this you will end up with data inconsistencies between Master and Slave servers. pt-table-checksum can help you here, which is found in Percona Toolkit for MySQL.
Last week I gave a talk at Percona MySQL University @Toronto about GTID. It includes an overview of MySQL 5.6 GTID that can help people to start working with this new feature in MySQL 5.6. Here are the slides from that session. I hope you find it useful: MySQL 5.6 GTID in a nutshell
最新文章
- MySQL基础笔记
- uboot的配置流程分析
- C#中的 特性 详解(转载)
- 一个新人眼中的O2O
- SQL笔记
- Ubuntu/Windows下利用“HIDAPI”库函数实现与Hid类USB设备通信
- 循序渐进开发WinForm项目（3)--Winform界面层的项目设计
- 018. ADO.NET _DataSet_DataAdapter
- HDOJ(HDU) 2519 新生晚会(组合公式)
- 做10年Windows程序员与做10年Linux程序员的区别（附无数评论）（开源软件相当于熟读唐诗三百首，不会作诗也会吟）
- inux中shell变量$#,$@,$0,$1,$2的含义
- python+NLTK 自然语言学习处理二：文本
- 联合线程（案例顾客买蛋糕 ：使用join()方法）
- 用API给用户添加职责
- Vue项目中使用基于Vue.js的移动组件库cube-ui
- vue文件上传控件
- redis 持久化共享 Session
- 未能加载文件或程序集“ .....WebUI ”或它的某一个依赖项，试图加载格式不正确的程序
- recovery 下界面UI旋转90 180 270修改
- Spark2.1.0模型设计与基本架构（上）