Skip to content

Commit df9c42e

Browse files
committed
fix typos
1 parent c63df25 commit df9c42e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/understanding-output.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ In the above we're mostly interested to see that `ETA: throttled, replica-lag=65
5959

6060
However another thing catches the eye: `Backlog: 0/100` transitions into `Backlog: 100/100`
6161

62-
- `Backlog` is the binlog events queue. A queue of events read from the binary log which are relevant for the migration. The queue gets emptied as events are applied onto the ghost table. Typically we want to see that queue empty or almost empty. However, due to the fact we're not throttled it makes perfect sense that the queue is full: htrottling means we do not apply events onto the ghost table, hence we do not purge the queue.
62+
- `Backlog` is the binlog events queue. A queue of events read from the binary log which are relevant for the migration. The queue gets emptied as events are applied onto the ghost table. Typically we want to see that queue empty or almost empty. However, due to the fact we're not throttled it makes perfect sense that the queue is full: throttling means we do not apply events onto the ghost table, hence we do not purge the queue.
6363

6464
```
6565
...
@@ -99,7 +99,7 @@ And `gh-ost` progressively provides an ETA.
9999

100100
Status frequency:
101101
- In the first `60` seconds `gh-ost` emits a status entry every `1` second.
102-
- Then, up till `3` miinutes into operation, status shows every `5` seconds.
102+
- Then, up till `3` minutes into operation, status shows every `5` seconds.
103103
- It then drops down to once per `30` seconds
104104
- But goes into once-per-`5`-seconds again when it estimates < `3` minutes ETA
105105
- And once per `1` second when it estimates < `1` minute ETA

0 commit comments

Comments
 (0)