Orchestrator is a MySQL topology manager and a failover solution, used in production on many large MySQL installments. It allows for detecting, querying and refactoring complex replication topologies, and provides reliable failure detection and intelligent recovery & promotion. This session walks through orchestrator setup, deployment and usage best practices. We will focus on major functionality points and share authoritative advice on practical production use. Our cheatsheet covers: Detection: - Name resolve - Classifying servers - Pool association Topologies: - Pseudo GTID configuration - Refactoring commands - Querying commands Failovers: - Basic configuration - Host promotion preferences - Hooks - Downtiming hosts - Anti flapping & acknowledgements - Planned failovers Scripting: - A putting-it-all-together use case for automating failover tests HA: - Making orchestrator highly available - Notes and thoughts about orchestrator's role in production Notes: - Supported/unsupported setups - Future plans Orchestrator is free and open source, and maintained by GitHub.
Senior Infrastructure Engineer, GitHub
Shlomi is an engineer and a database geek. He is an active MySQL community member, authors gh-ost, orchestrator, common_schema and other open source tools, and blogs at http://openark.org. Shlomi is recipient of Oracle ACE, Oracle Technologist of the Year, and MySQL Community Member of the Year awards. He works at GitHub on the database infrastructure team.