One VTOrc To Rule Them All – High Availability In a Distributed Database System
summary
Vitess cluster management service VTOrc is a replacement orchestrator that is GA in Vitess 15 and already runs in production at PlanetScale, performing automated failure detection and both planned and unplanned failovers. It uses the topology server (etcd/zookeeper/consul), enforces configurable durability policies (semi‑sync acks, cross‑cell rules), and demoed a 4‑replica keyspace where VTOrc promotes secondaries, refuses unsafe promotions (avoiding split‑brain), and requires quorum intersection via the tunable M parameter.
AI-written summary · about
chapters (10)
- 0:00Vitess overview
- 1:54Architecture and VTArc
- 3:18VTArc mission and design
- 5:58Consensus and design goals
- 8:27Leader election process
- 12:39Durability policies
- 14:47Quorums and safety
- 17:37Demonstrations
- 24:52Implementing custom policies
- 26:34Q&A session
related talks
35mExploring High Availability in Kubernetes with Vitess
45mDeep Dive: Vitess
35mExploring High Availability in Kubernetes with Vitess
43mVitess and a Kubernetes Operator
34mInside Vitess: Building Resilient, Distributed Databases
40mVitess: Intro and New Features
31mVitess: Running MySQL with confidence on Kubernetes
44mIntro: Vitess