Skip to content

Commit 0210c3b

Browse files
Reorder doc
Signed-off-by: Tim Vaillancourt <[email protected]>
1 parent 52574ef commit 0210c3b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/command-line-flags.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -102,13 +102,13 @@ This is somewhat similar to a Nagios `n`-times test, where `n` in our case is al
102102

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

105-
### cut-over-lock-timeout-seconds
105+
### cut-over-idle-timeout-seconds
106106

107-
Default `3`. Max number of seconds to hold locks on tables while attempting to cut-over (retry attempted when lock exceeds timeout).
107+
When set to a value greater than zero, this flag causes `gh-ost` to set a [MySQL `wait_timeout`](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_wait_timeout) for the MySQL session performing the cut-over, specified in seconds. This timeout is to ensure the locks held by the cut-over are released if the `gh-ost` process becomes unresponsive _(but still alive)_ mid-cut-over.
108108

109-
### cut-over-wait-timeout-seconds
109+
### cut-over-lock-timeout-seconds
110110

111-
When set to a value greater than zero, this flag causes `gh-ost` to set a [MySQL `wait_timeout`](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_wait_timeout) for the MySQL session performing the cut-over, specified in seconds. This timeout is to ensure the locks held by the cut-over are released if the `gh-ost` process becomes unresponsive _(but still alive)_ mid-cut-over.
111+
Default `3`. Max number of seconds to hold locks on tables while attempting to cut-over (retry attempted when lock exceeds timeout).
112112

113113
### discard-foreign-keys
114114

0 commit comments

Comments
 (0)