Auto-merged master into check-lag-on-starting on deployment
This commit is contained in:
commit
b5c606a38b
@ -60,6 +60,7 @@ Also see:
|
||||
- [requirements and limitations](doc/requirements-and-limitations.md)
|
||||
- [what if?](doc/what-if.md)
|
||||
- [the fine print](doc/the-fine-print.md)
|
||||
- [Questions](https://github.com/github/gh-ost/issues?q=label%3Aquestion)
|
||||
|
||||
## What's in a name?
|
||||
|
||||
|
@ -47,7 +47,7 @@ Initial setup is a no-concurrency operation
|
||||
- Applying `alter` on ghost table
|
||||
- Comparing structure of original & ghost table. Looking for shared columns, shared unique keys, validating foreign keys. Choosing shared unique key, the key by which we chunk the table and process it.
|
||||
- Setting up the binlog listener; begin listening on changelog events
|
||||
- Injecting a "good to go" ebtry onto the changelog table (to be intercepted via binary logs)
|
||||
- Injecting a "good to go" entry onto the changelog table (to be intercepted via binary logs)
|
||||
- Begin listening on binlog events for original table DMLs
|
||||
- Reading original table's chosen key min/max values
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user