From 5773fd22aeb9240d79de63a4e4664762db8745e7 Mon Sep 17 00:00:00 2001 From: Shlomi Noach Date: Thu, 1 Sep 2016 13:12:24 +0200 Subject: [PATCH] more comments on cut-over --- doc/cut-over.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/cut-over.md b/doc/cut-over.md index b1aaf6d..ada5100 100644 --- a/doc/cut-over.md +++ b/doc/cut-over.md @@ -15,3 +15,7 @@ This solution either: Also note: - With `--migrate-on-replica` the cut-over is executed in exactly the same way as on master. - With `--test-on-replica` the replication is first stopped; then the cut-over is executed just as on master, but then reverted (tables rename forth then back again). + +Internals of the atomic cut-over are discussed in [Issue #82](https://github.com/github/gh-ost/issues/82). + +At this time the command-line argument `--cut-over` is supported, and defaults to the atomic cut-over algorithm described above. Also supported is `--cut-over=two-step`, which uses the FB non-atomic algorithm. We recommend using the default cut-over that has been battle tested in our production environments.