From f710ca6772d98eeb897aaa339f61d7c55e42e427 Mon Sep 17 00:00:00 2001 From: Ivan Groenewold Date: Tue, 7 Feb 2017 10:56:28 -0300 Subject: [PATCH 1/2] additional info re: Tungsten --- doc/cheatsheet.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/cheatsheet.md b/doc/cheatsheet.md index 223f47c..9db8467 100644 --- a/doc/cheatsheet.md +++ b/doc/cheatsheet.md @@ -146,8 +146,12 @@ gh-ost --allow-master-master --assume-master-host=a.specific.master.com Topologies using _tungsten replicator_ are peculiar in that the participating servers are not actually aware they are replicating. The _tungsten replicator_ looks just like another app issuing queries on those hosts. `gh-ost` is unable to identify that a server participates in a _tungsten_ topology. -If you choose to migrate directly on master (see above), there's nothing special you need to do. If you choose to migrate via replica, then you must supply the identity of the master, and indicate this is a tungsten setup, as follows: +If you choose to migrate directly on master (see above), there's nothing special you need to do. + +If you choose to migrate via replica, then you need to make sure Tungsten is configured with log-slave-updates parameter (note this is different from MySQL's own log-slave-updates parameter), otherwise changes will not be in the replica's binlog, causing data to be corrupted after table swap. You must also supply the identity of the master, and indicate this is a tungsten setup, as follows: ``` gh-ost --tungsten --assume-master-host=the.topology.master.com ``` + +Also note that `--switch-to-rbr` does not work for a Tungsten setup as the replication process is external, so you need to make sure `binlog_format` is set to ROW beforehand. From fbf88fd57127d05a8d1f449c6918b2d3a1e23f72 Mon Sep 17 00:00:00 2001 From: Ivan Groenewold Date: Tue, 7 Feb 2017 11:45:20 -0300 Subject: [PATCH 2/2] additional note for Tungsten and rbr --- doc/cheatsheet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/cheatsheet.md b/doc/cheatsheet.md index 9db8467..6ff9682 100644 --- a/doc/cheatsheet.md +++ b/doc/cheatsheet.md @@ -154,4 +154,4 @@ If you choose to migrate via replica, then you need to make sure Tungsten is con gh-ost --tungsten --assume-master-host=the.topology.master.com ``` -Also note that `--switch-to-rbr` does not work for a Tungsten setup as the replication process is external, so you need to make sure `binlog_format` is set to ROW beforehand. +Also note that `--switch-to-rbr` does not work for a Tungsten setup as the replication process is external, so you need to make sure `binlog_format` is set to ROW before Tungsten Replicator connects to the server and starts applying events from the master.