Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update the description of the max-lag-millis in docs #1388

Merged
merged 3 commits into from
Mar 12, 2024
Merged

Update the description of the max-lag-millis in docs #1388

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0ca1dfc
Update description for max-lag-millis in command-line-flags.md
dontstopbelieveing Mar 9, 2024
c55c34d
Update command-line-flags.md
dontstopbelieveing Mar 9, 2024
78821e6
Merge branch 'master' into master
timvaillancourt Mar 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions doc/command-line-flags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -190,6 +190,8 @@ When using [Connect to replica, migrate on master](cheatsheet.md#a-connect-to-re

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.

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.

See also: [Sub-second replication lag throttling](subsecond-lag.md)

### max-load
Expand Down