Orchestrator 1.4.340 is released. Not quite competing with the MySQL latest changelog, and asĀ I haven’t blogged about orchestrator featureset in a while, this isĀ a quick listing of orchestrator features available since my lastĀ publication:
- Supports GTID (Oracle & MariaDB)
- GTID still not being used in automated recovery — in progress.
- enable-gtid, disable-gtid, skip-query for GTID commands
- Supports binlog servers (MaxScale)
- Discovery & operations on binlog servers
- Understanding slave repositioning in a binlog-server architecture
- Smart mode: relocate & relocate-below commands (or Web/GUI drag-n-drop) let orchestrator figure out the best way of slave repositioning. Orchestrator picks from GTID, Pseudo GTID, binlog servers, binlog file:pos math (and more) options, or combinations of the above.Ā Fine grained commands still there, but mostly you won’t need them.
- Crash recoveries (did you know orchestrator does that?):
- For intermediate master recovery: improved logic in picking the best recovery plan (prefer in-DC, prefer promoting local slave, supporting binlog server topologies, …)
- For master recovery: even better slave promotion; supports candidate slaves (prefer promoting such slaves); supports binlog server shared topologies
- Better auditing and logging of recovery cases
- Better analysis of crash scenarios, also in the event of lost VIPs, hanging connections; emergent checks in crash suspected scenarios
- recover-lite: do all topology-only recovery steps, without invoking external processes
- Better browser support: used to only work onĀ Firefox and Chrome (and the latter has had issues), the Web UI should now work well on all browsers, at the cost of reduced d3 animation. More work still in progress.
- Faster, more parallel, less blocking operations on all counts; removed a lots of serialized code; less locks.
- Web enhancements
- More verbose drag-n-drop (operation hint; color hints)
- Drag-n-drop for slaves-of-a-server
- Replication/crash analysis dashboard
- Pools: orchestrator can be told about instance-to-pool association (submit-pool-instances command)
- And can then present pool status (web)
- Or pool hints within topologies (web)
- Or queried for all pools (cluster-pool-instances command)
- Other:
- Supports MySQL 5.7 (tested with 5.7.8)
- Configurable graphite path for metrics
- –noop flag; does all the work except for actually changing master on slaves. Shows intentions.
- Web (or cliĀ which-cluster-osc-slaves command) provide list of control slaves to use in pt-osc operation
- hostname-unresolve: force orchestrator to unresolve a fqdn into VIP/CNAME/… when issuing a CHANGE MASTER TO
- 3rd party contributions (hey, thanks!) include:
- More & better SSL support
- Vagrant templates
- For developers:
- Orchestrator now go-gettable. Just go getĀ github.com/outbrain/orchestrator
- Improved build script; supports more architectures
Also consider these manuals:
- The Orchestrator Manual
- Orchestrator deployment
- Orchestrator first steps
- Orchestrator for developers
Orchestrator is free and open source (Apache 2.0 License).
I’ll be speaking about orchestrator in PerconaLive Amsterdam.