Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/outbrain/orchestrator
MySQL replication topology manager/visualizer
https://github.com/outbrain/orchestrator
Last synced: about 1 month ago
JSON representation
MySQL replication topology manager/visualizer
- Host: GitHub
- URL: https://github.com/outbrain/orchestrator
- Owner: outbrain
- License: other
- Created: 2014-04-24T12:06:37.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2020-07-26T17:12:05.000Z (over 4 years ago)
- Last Synced: 2024-08-01T08:07:16.885Z (4 months ago)
- Language: Go
- Size: 5.43 MB
- Stars: 827
- Watchers: 94
- Forks: 168
- Open Issues: 40
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-go-storage - orchestrator - MySQL replication topology manager & visualizer (Database)
- awesome-repositories - outbrain/orchestrator - MySQL replication topology manager/visualizer (Go)
README
# orchestrator upstream has moved
**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.
---
orchestrator [[Manual]](https://github.com/outbrain/orchestrator/wiki/Orchestrator-Manual)
============
_Orchestrator_ is a MySQL replication topology management and visualization tool, allowing for:
#### Discovery
_orchestrator_ actively crawls through your topologies and maps them. It reads basic MySQL info such as replication status and configuration.
It provides with slick visualization of your topologies, including replication problems, even in the face of failures.
#### Refactoring
_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 slaves around becomes
safe: _orchestrator_ will reject an illegal refactoring attempt.
Find grained control is achieved by various command line options.
#### Recovery
_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.
#### More
- Auditing
- Supports Pseudo-GTID
- Datacenter/physical location awareness
- Maintenenace/downtime server states
- MySQL-Pool association
- Run as a service; orchestrator multi-service HA
- HTTP security/authentication methods
- When working with [orchestrator-agent](https://github.com/outbrain/orchestrator-agent), seed new/corrupt instances
- More...
Read the [Orchestrator Manual](https://github.com/outbrain/orchestrator/wiki/Orchestrator-Manual) for comprehensive documentation.
Authored by [Shlomi Noach](https://github.com/shlomi-noach) at [GitHub](http://github.com). Previously at [Booking.com](http://booking.com) and [Outbrain](http://outbrain.com)