-
Notifications
You must be signed in to change notification settings - Fork 168
FAQ
NOTE: orchestrator development is now active on https://github.com/github/orchestrator, where Issues and Pull Requests are accepted.
This repository is no longer the upstream and latest version of orchestrator.
The documentation in this repository is not up-to-date.
DBAs and ops who have more than a mere single-master-single-slave replication topology.
Orchestrator analyzes your replication topologies. It can visualize those topologies, and it allows you to move slaves around the topology easily and safely. It provides full audit to operations making for a topology changelog. It can serve as a command line tool or it can provide with JSON API for all operations.
No. Orchestrator is strictly not a monitoring tool. There is no intention to make it so; no alerts or emails. It does provide with online visualization of your topology status though, and requires some thresholds of its own in order to manage the topology.
Orchestrator supports "plain-old-MySQL-replication", the one that uses binary log files and positions. If you don't know what you're using, this is probably the one. It is the only type of replication up to and including MySQL 5.5.
Yes. Statement Based Replication and Row Based Replication are both supported (and the distinction is in fact irrelevant to orchestrator)
Yes. And orchestrator is in fact ignorant about it.
Yes, for a ring of two masters (active-active, active-passive).
Master-Master-Master[-Master...] topologies, where the ring is composed of 3 or more masters are not supported and not tested. And are discouraged. And are an abomination.
Yes and no. Orchestrator is unaware of Galera replication. If you have three Galera masters and different slave topologies under each master, then orchestrator sees these as three different topologies.
Yes. Both Oracle GTID and MariaDB GTID are supported.
No. This is because START SLAVE UNTIL is not supported in parallel replication, and output of SHOW SLAVE STATUS is incomplete.
There is no expected work on this.
Yes, when in-order-replication is enabled (see slave_preserve_commit_order). The same applies to MariaDB.
No. Multi Master Replication (e.g. as in MariaDB 10.0) is not supported.
No.
No.
No.
Yes. Orchestrator is released as open source under the Apache 2.0 license and is available at: https://github.com/outbrain/orchestrator
Orchestrator is developed by Shlomi Noach at Booking.com (previously at Outbrain) to assist in managing multiple large replication topologies; time and human errors saved so far are almost priceless.