adding documentation
This commit is contained in:
parent
a9d4c11aa1
commit
8102c90ee2
@ -9,7 +9,8 @@ Test on replica if you:
|
|||||||
|
|
||||||
## What testing on replica means
|
## What testing on replica means
|
||||||
|
|
||||||
`gh-ost` will make all changes
|
TL;DR `gh-ost` will make all changes on a replica and leave both original and ghost tables for you to compare.
|
||||||
|
|
||||||
## Issuing a test drive
|
## Issuing a test drive
|
||||||
|
|
||||||
Apply `--test-on-replica --host=<a.replica>`.
|
Apply `--test-on-replica --host=<a.replica>`.
|
||||||
@ -36,7 +37,6 @@ You now have the time to verify the tool works correctly. You may checksum the e
|
|||||||
- or of course only select the shared columns before/after the migration
|
- or of course only select the shared columns before/after the migration
|
||||||
- We use the trivial `engine=innodb` for `alter` when testing. This way the resulting ghost table is identical in structure to the original table (including indexes) and we expect data to be completely identical. We use `md5sum` on the entire dataset to confirm the test result.
|
- We use the trivial `engine=innodb` for `alter` when testing. This way the resulting ghost table is identical in structure to the original table (including indexes) and we expect data to be completely identical. We use `md5sum` on the entire dataset to confirm the test result.
|
||||||
|
|
||||||
|
|
||||||
### Cleanup
|
### Cleanup
|
||||||
|
|
||||||
It's your job to:
|
It's your job to:
|
||||||
|
Loading…
Reference in New Issue
Block a user