Skip to content

Commit bc6cd55

Browse files
Update the description of the max-lag-millis in docs (#1388)
* Update description for max-lag-millis in command-line-flags.md * Update command-line-flags.md --------- Co-authored-by: Tim Vaillancourt <[email protected]>
1 parent 48b34bc commit bc6cd55

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

doc/command-line-flags.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -190,6 +190,8 @@ When using [Connect to replica, migrate on master](cheatsheet.md#a-connect-to-re
190190

191191
When [`--throttle-control-replicas`](#throttle-control-replicas) is provided, throttling also considers lag on specified hosts. Lag measurements on listed hosts is done by querying `gh-ost`'s _changelog_ table, where `gh-ost` injects a heartbeat.
192192

193+
When using on master or when `--allow-on-master` is provided, `max-lag-millis` is also considered a threshold for starting the cutover stage of the migration. If the row copy is complete and the heartbeat lag is less than `max-lag-millis` cutover phase of the migration will start.
194+
193195
See also: [Sub-second replication lag throttling](subsecond-lag.md)
194196

195197
### max-load

0 commit comments

Comments
 (0)