Easy Geo-Redundant Handover + Failover with MARS + systemd
summary
Long-distance, transaction-logged replication using MARS transaction-logged replication and a new systemd unit-template generator automates geo-handover so a secondary can become primary while preserving strict local consistency and propagating sibling-tree state. Production MARS backs thousands of LXC containers and several petabytes at 1&1 IONOS since 2014; the new systemd interface is functional but not yet deployed at scale and currently uses breakable locks to work around a reentrancy deadlock in systemctl. Metadata scalability tops out around 14 generated resources today.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:21Easy Geo-Redundant Handover+Fallover: Agenda
- 3:04Cluster Management for 50 km
- 6:13systend Unit Example Template
- 8:30Current status of systemd interface
- 9:25Usage of systend unit templates
- 12:25Current status of system interface
- 14:40MARS Future Plans
related talks
01h 08mMARS: Replicating Petabytes over Long Distances
43mHot Deploying Low-Latency Services for 24/7 Operation
59mRunning a real world, mission-critical system on Azure
25mEvolution of Geo-replication in Gluster
53mMulti master replication for painless fault tolerance
42mUsing Mesos to Drive Devops Adoption at Scale
47mDeploying Like a Boss: From 2 Servers to 20,000
18mLeveraging Multiple Regions to Improve Site Reliability:
