Orchestrator uses Raft consensus as of version 3.x. This setup improves the high availability of both the orchestrator service itself as well as that of the managed topologies and allows for easier operations.
This session will briefly introduce Raft consensus concepts, and elaborate on orchestrator's use of Raft: from leader election, through high availability, cross DC deployments and DC fencing mitigation, and lightweight deployments with SQLite.
Of course, nothing comes for free, and we will discuss considerations to using Raft: expected impact, eventual consistency and time-based assumptions.
Orchestrator/Raft is running in production at GitHub, Wix and other large and busy deployments.
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 works at GitHub on the database infrastructure team solving high availability, reliability, enablement, automation and testing. Previously he managed high availability of X,000 of MySQL servers at Booking.com, and solved infrastructure problems at Outbrain. He is recipient of Oracle ACE, Oracle Technologist of the Year, and MySQL Community Member of the Year awards.