From 914f692af2888edacead61eca911455448c982da Mon Sep 17 00:00:00 2001 From: Shlomi Noach Date: Wed, 4 Jan 2017 08:30:23 +0200 Subject: [PATCH] grammar --- 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 564d337..5152978 100644 --- a/doc/subsecond-lag.md +++ b/doc/subsecond-lag.md @@ -14,6 +14,6 @@ In both cases, `gh-ost` uses an internal heartbeat mechanism. It injects heartbe You can explicitly define how frequently will `gh-ost` inject heartbeat events, via `heartbeat-interval-millis`. You should set `heartbeat-interval-millis <= max-lag-millis`. It still works if not, but loses granularity and effect. -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. +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 is 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 `--max-lag-millis` value of between `300` and `500`.