You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
148
148
149
-
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:
149
+
If you choose to migrate directly on master (see above), there's nothing special you need to do.
150
+
151
+
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:
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.
Copy file name to clipboardExpand all lines: doc/interactive-commands.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,9 @@ Both interfaces may serve at the same time. Both respond to simple text command,
26
26
- The `critical-load` format must be: `some_status=<numeric-threshold>[,some_status=<numeric-threshold>...]`'
27
27
- For example: `Threads_running=1000,threads_connected=5000`, and you would then write/echo `critical-load=Threads_running=1000,threads_connected=5000` to the socket.
28
28
-`nice-ratio=<ratio>`: change _nice_ ratio: 0 for aggressive (not nice, not sleeping), positive integer `n`:
29
-
- For any `1ms` spent copying rows, spend `n*1ms` units of time sleeping.
30
-
- Examples: assume a single rows chunk copy takes `100ms` to complete.
31
-
-`nice-ratio=0.5` will cause `gh-ost` to sleep for `50ms` immediately following.
29
+
- For any `1ms` spent copying rows, spend `n*1ms` units of time sleeping.
30
+
- Examples: assume a single rows chunk copy takes `100ms` to complete.
31
+
-`nice-ratio=0.5` will cause `gh-ost` to sleep for `50ms` immediately following.
32
32
-`nice-ratio=1` will cause `gh-ost` to sleep for `100ms`, effectively doubling runtime
33
33
- value of `2` will effectively triple the runtime; etc.
34
34
-`throttle-query`: change throttle query
@@ -38,6 +38,10 @@ Both interfaces may serve at the same time. Both respond to simple text command,
38
38
-`unpostpone`: at a time where `gh-ost` is postponing the [cut-over](cut-over.md) phase, instruct `gh-ost` to stop postponing and proceed immediately to cut-over.
39
39
-`panic`: immediately panic and abort operation
40
40
41
+
### Querying for data
42
+
43
+
For commands that accept an argumetn as value, pass `?` (question mark) to _get_ current value rather than _set_ a new one.
0 commit comments