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
Copy file name to clipboardExpand all lines: doc/interactive-commands.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,8 @@ Both interfaces may serve at the same time. Both respond to simple text command,
19
19
-`throttle`: force migration suspend
20
20
-`no-throttle`: cancel forced suspension (though other throttling reasons may still apply)
21
21
-`chunk-size=<newsize>`: modify the `chunk-size`; applies on next running copy-iteration
22
+
-`max-load=<max-load-thresholds>`: modify the `max-load` config; applies on next running copy-iteration
23
+
The `max-load` format must be: `some_status=<numeric-threshold>[,some_status=<numeric-threshold>...]`. For example: `Threads_running=50,threads_connected=1000`, and you would then write/echo `max-load=Threads_running=50,threads_connected=1000` to the socket.
0.`gh-ost` creates and uses a changelog table for internal bookkeeping. This table has the `_osc` suffix (the tool creates and announces this table upon startup) If you like, you can SQL your status:
43
+
2.`gh-ost` creates and uses a changelog table for internal bookkeeping. This table has the `_osc` suffix (the tool creates and announces this table upon startup) If you like, you can SQL your status:
35
44
36
45
```
37
46
> select * from _sample_data_0_osc order by id desc limit 1 \G
Copy file name to clipboardExpand all lines: doc/why-triggerless.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,10 @@ Thus, triggers must keep operating. On busy servers, we have seen that even as t
45
45
46
46
Read more about [`gh-ost` throttling](throttle.md)
47
47
48
+
### Triggers, multiple migrations
49
+
50
+
We are interested in being able to run multiple concurrent migrations (not on the same table, of course). Given all the above, we do not have trust that running multiple trigger-based migrations is a safe operation. In our current, past and shared experiences we have never done so; we are unaware of anyone who is doing so.
51
+
48
52
### Trigger based migration, no reliable production test
49
53
50
54
We sometimes wish to experiment with a migration, or know in advance how much time it would take. A trigger-based solution allows us to run a migration on a replica, provided it uses Statement Based Replication.
0 commit comments