From 25e2d29a1ee07c3dc2a5c3070f295e3e12a7384b Mon Sep 17 00:00:00 2001 From: Shlomi Noach Date: Sat, 16 Jul 2016 10:59:43 -0600 Subject: [PATCH 1/2] more doc --- README.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 5b84d1657..053132608 100644 --- a/README.md +++ b/README.md @@ -75,7 +75,19 @@ Pronounce: _ghost_ `gh-ost` is released at a stable state, but with mileage to go. We are [open to pull requests](https://github.com/github/gh-ost/blob/master/.github/CONTRIBUTING.md). Please first discuss your intentions via [Issues](https://github.com/github/gh-ost/issues). -We develop `gh-ost` at GitHub and for the community. We may have different priorities than others. From time to time we may suggest a contribution that is not on our immediate roadmap but which may appeal to others. +We develop `gh-ost` at GitHub and for the community. We may have different priorities than others. From time to time we may suggest a contribution that is not on our immediate roadmap but which may appeal to others. + +## Download/binaries/source + +`gh-ost` is now GA and stable. + +`gh-ost` is available in binary format for Linux and Mac OS/X + +[Download latest release here](https://github.com/github/gh-ost/releases/latest) + +`gh-ost` is a Go project; it is built with Go 1.5 with "experimental vendor". Soon to migrate to Go 1.6. See and use [build file](https://github.com/github/gh-ost/blob/master/build.sh) for compiling it on your own. + +Generally speaking, `master` branch is stable, but only [releases](https://github.com/github/gh-ost/releases) are to be used in production. ## Authors From a0e10a17d8c3a7d1d06062d0f9d88a98c006c043 Mon Sep 17 00:00:00 2001 From: Shlomi Noach Date: Tue, 19 Jul 2016 16:40:50 -0600 Subject: [PATCH 2/2] more what-if --- doc/what-if.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/what-if.md b/doc/what-if.md index c457fab2c..62db3eecb 100644 --- a/doc/what-if.md +++ b/doc/what-if.md @@ -30,3 +30,13 @@ There is a `lock_wait_timeout` explicitly associated with the cut-over operation This is where `gh-ost` shines. There is no need to kill it as you may be used to with other tools. You can reconfigure `gh-ost` [on the fly](https://github.com/github/gh-ost/blob/master/doc/interactive-commands.md) to be nicer. You're always able to actively begin [throttling](throttle.md). Just touch the `throttle-file` or `echo throttle` into `gh-ost`. Otherwise, reconfigure your `max-load`, the `nice-ratio`, the `throttle-query` to gain better thresholds that would suit your needs. + +### What if my replicas don't use binary logs? + +If the master is running Row Based Replication (RBR) - point `gh-ost` to the master, and specify `--allow-on-master`. See [cheatsheets](cheatsheets.md) + +If the master is running Statement Based Replication (SBR) - you have no alternative but to reconfigure a replica with: + +- `log_bin` +- `log_slave_updates` +- `binlog_format=ROW`