octoleo/gh-ost
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Grammar fix

Browse Source 
Co-authored-by: Rashiq <rashiq@users.noreply.github.com>
This commit is contained in:
Alon Pe'er 2021-09-15 13:15:42 +02:00 committed by GitHub
parent 08f4e34dd9
commit 9a67740c1e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/cut-over.md
View File

@ -12,7 +12,7 @@ lock command, and like the cut-over should take a little time it shouldn't be a
- A stop writes event is injected in the binlog and gh-ost disable the writes once it receive it.
- The triggers are created to handle the modifications in the MySQL side.
- A created triggers event is injected in the binlog and gh-ost wait until receive it.
- A created triggers event is injected in the binlog and gh-ost waits until it receive it.
- The affected rows will be in an inconsistent stata during the time between the first and the second event. For this reason, this events are checked and, the values of the fields that are part of the unique key used to do the online alter are saved to sanitize that rows.
`gh-ost` solves this by using an atomic, two-step blocking swap: while one connection holds the lock, another attempts the atomic `RENAME`. The `RENAME` is guaranteed to not be executed prematurely by positioning a sentry table which blocks the `RENAME` operation until `gh-ost` is satisfied all is in order.