DM運維踩坑實踐總結

{"type":"doc","content":[{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"背景"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在早期從MySQL到TiDB實施同步操作過程中,我們大多數用的是mydumper+loader進行整體全量備份的導出,之後拿到meta信息後,通過syncer實現增量同步,整體操作起來比較麻煩,涉及的配置文件較多,其基本原理就是Syncer 通過把自己註冊爲一個 MySQL Slave 的方式,和 MySQL Master 進行通信,然後不斷讀取 MySQL Binlog,進行 Binlog Event 解析,規則過濾和數據同步。其架構如下:"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/static001.infoq.cn\/resource\/image\/c0\/3b\/c01b24ac6a5a35f635f779640bbe413b.png","alt":null,"title":"","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":"","fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"而後pingcap官方推出了TiDB Data Migration (DM)套件,這一套件極大地降低了同步工具使用的門檻。DM是一體化的數據遷移任務管理平臺,支持從 MySQL 或 MariaDB 到 TiDB 的全量數據遷移和增量數據複製。使用 DM 工具有利於簡化錯誤處理流程,降低運維成本。後續更是有dm-portal工具方便dba通過圖形化界面的方式進行選擇性導出和自動生成配置文件,雖然有一些小bug和不夠人性化的方面,但無傷大雅,可惜的是這個項目最後諮詢官方得知被砍掉了,不再進行維護。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"原因"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}}]}
發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章