Skip to content

Commit 53f7d69

Browse files
author
Shlomi Noach
committed
documentation for --critical-load-interval-millis flag
1 parent 15f4ddf commit 53f7d69

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

doc/command-line-flags.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,16 @@ password=123456
4343

4444
See `exact-rowcount`
4545

46+
### critical-load-interval-millis
47+
48+
`--critical-load` defines a threshold that, when met, `gh-ost` panics and bails out. The default behavior is to bail out immediately when meeting this threshold.
49+
50+
This may sometimes lead to migrations bailing out on a very short spike, that, while in itself is impacting production and is worth investigating, isn't reason enough to kill a 10 hour migration.
51+
52+
When `--critical-load-interval-millis` is specified (e.g. `--critical-load-interval-millis=2500`), `gh-ost` gives a second chance: when it meets `critical-load` threshold, it doesn't bail out. Instead, it starts a timer (in this example: `2.5` seconds) and re-checks `critical-load` when the timer expires. If `critical-load` is met again, `gh-ost` panics and bails out. If not, execution continues.
53+
54+
This is somewhat similar to a Nagios `n`-times test, where `n` in our case is always `2`.
55+
4656
### cut-over
4757

4858
Optional. Default is `safe`. See more discussion in [cut-over](cut-over.md)

0 commit comments

Comments
 (0)