You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Shlomi Noach c85d65f9d6
Merge pull request #1349 from akatashev/fix_reverse_proxy_authorization
2 weeks ago
.github extract apt-get update to separate step 11 months ago
conf Add Consul KV store based on atomic transactions 6 months ago
docker Adding Dockerfile.raft, 'script/dock raft' environemtn 11 months ago
docs Merge branch 'master' into patch-3 2 weeks ago
etc etc adapting to code change to 1 year ago
go Remove setting request credentials in reverse-proxy 2 weeks ago
resources removed non-compressed files 1 month ago
script Merge pull request #1349 from akatashev/fix_reverse_proxy_authorization 2 weeks ago
tests recover NoWriteableMasterStructureWarning 2 months ago
vagrant vagrant adapting to code change to 1 year ago
vendor update go-sql-driver/mysql to latest 4 weeks ago
.dockerignore Fix docker build after c419404f996ee7c9f879dd756d06ed65ef2103c4 4 years ago
.gitignore gitignore: .vscode 11 months ago
.go-version added .go-version hint, requires 1.5 5 years ago
.project refactored to go gettable; Fixed ChangeMAsterTo bug in unresolve (hidden local variable); Fixed read-recoveries for active/recent 6 years ago
LICENSE copyright update 1 year ago add python-mysql-orchestrator to related projects 9 months ago
RELEASE_VERSION v3.2.4 3 months ago
Vagrantfile return rsync shared folder back 3 years ago Expect and use go1.14 11 months ago
bump_release_version_and_tag renamed variable 4 years ago

downloads release

orchestrator [Documentation]

Orchestrator logo

orchestrator is a MySQL high availability and replication management tool, runs as a service and provides command line access, HTTP API and Web interface. orchestrator supports:


orchestrator actively crawls through your topologies and maps them. It reads basic MySQL info such as replication status and configuration.

It provides you with slick visualization of your topologies, including replication problems, even in the face of failures.


orchestrator understands replication rules. It knows about binlog file:position, GTID, Pseudo GTID, Binlog Servers.

Refactoring replication topologies can be a matter of drag & drop a replica under another master. Moving replicas around is safe: orchestrator will reject an illegal refactoring attempt.

Fine-grained control is achieved by various command line options.


orchestrator uses a holistic approach to detect master and intermediate master failures. Based on information gained from the topology itself, it recognizes a variety of failure scenarios.

Configurable, it may choose to perform automated recovery (or allow the user to choose type of manual recovery). Intermediate master recovery achieved internally to orchestrator. Master failover supported by pre/post failure hooks.

Recovery process utilizes orchestrator's understanding of the topology and of its ability to perform refactoring. It is based on state as opposed to configuration: orchestrator picks the best recovery method by investigating/evaluating the topology at the time of recovery itself.

The interface

orchestrator supports:

  • Command line interface (love your debug messages, take control of automated scripting)
  • Web API (HTTP GET access)
  • Web interface, a slick one.

Orcehstrator screenshot

Additional perks

  • Highly available
  • Controlled master takeovers
  • Manual failovers
  • Failover auditing
  • Audited operations
  • Pseudo-GTID
  • Datacenter/physical location awareness
  • MySQL-Pool association
  • HTTP security/authentication methods
  • There is also an orchestrator-mysql Google groups forum to discuss topics related to orchestrator
  • More...

Read the Orchestrator documentation

Authored by Shlomi Noach:


Get started developing Orchestrator by reading the developer docs. Thanks for your interest!


orchestrator is free and open sourced under the Apache 2.0 license.