From 3bf64d8280b7cd639c95f748ccff02e90a7f4345 Mon Sep 17 00:00:00 2001 From: Shlomi Noach Date: Tue, 27 Dec 2016 09:16:27 +0200 Subject: [PATCH] typo --- doc/subsecond-lag.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/subsecond-lag.md b/doc/subsecond-lag.md index c786ca2..564d337 100644 --- a/doc/subsecond-lag.md +++ b/doc/subsecond-lag.md @@ -16,4 +16,4 @@ You can explicitly define how frequently will `gh-ost` inject heartbeat events, In earlier versions, the `--throttle-control-replicas` list was subjected to `1` second resolution or to 3rd party heartbeat injections such as `pt-heartbeat`. This is no longer the case. The argument `--replication-lag-query` has been deprecated and no longer needed. -Our production migrations use sub-second lag throttling and are able to keep our entire fleet of replicas well below `1sec` lag. We use `--heartbeat-interval-millis=100` on our production migrations with a `--mas-lag-millis` value of between `300` and `500`. +Our production migrations use sub-second lag throttling and are able to keep our entire fleet of replicas well below `1sec` lag. We use `--heartbeat-interval-millis=100` on our production migrations with a `--max-lag-millis` value of between `300` and `500`.