Remove resetting Auth credentials in reverse-proxy
|2 weeks ago|
|.github||11 months ago|
|conf||6 months ago|
|docker||11 months ago|
|docs||2 weeks ago|
|etc||1 year ago|
|go||2 weeks ago|
|resources||1 month ago|
|script||2 weeks ago|
|tests||2 months ago|
|vagrant||1 year ago|
|vendor||4 weeks ago|
|.dockerignore||4 years ago|
|.gitignore||11 months ago|
|.go-version||5 years ago|
|.project||6 years ago|
|LICENSE||1 year ago|
|README.md||9 months ago|
|RELEASE_VERSION||3 months ago|
|Vagrantfile||3 years ago|
|build.sh||11 months ago|
|bump_release_version_and_tag||4 years ago|
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 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
- Command line interface (love your debug messages, take control of automated scripting)
- Web API (HTTP GET access)
- Web interface, a slick one.
- Highly available
- Controlled master takeovers
- Manual failovers
- Failover auditing
- Audited operations
- 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
Read the Orchestrator documentation
Authored by Shlomi Noach:
- 2020- as https://github.com/openark/orchestrator
- 2016-2020 at GitHub as https://github.com/github/orchestrator
- 2015 at Booking.com as https://github.com/outbrain/orchestrator
- 2014 at Outbrain as https://github.com/outbrain/orchestrator
- Orchestrator Puppet module: https://github.com/github/puppet-orchestrator-for-mysql
- Orchestrator Chef Cookbook (1): https://github.com/silviabotros/chef-orchestrator
- Orchestrator Chef Cookbook (2): https://supermarket.chef.io/cookbooks/orchestrator
- Nagios / Icinga check based on Orchestrator API: https://github.com/mcrauwel/go-check-orchestrator
- Light Python wrapper for Orchestrator API: https://github.com/stirlab/python-mysql-orchestrator
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.