Protecting your resources with sanlock
summary
Sanlock implements Disk Paxos for fast per-resource leases and Delta leases to assign unique host IDs and liveness, writing one atomic block per host to shared storage. Host IDs are limited to 2,000 hosts by a hardcoded layout, and the lockspace is initialized once. Leases must be refreshed roughly every 20 seconds (small delta ~10s); failure to renew triggers fencing/watchdog that can kill the node. Paxos leases are quick; setup and timeouts matter.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:35Motivation
- 1:30External Work Manager
- 2:20Work Manager
- 3:53Axis
- 4:50Paxos
- 9:00Disks
- 10:40Unanswered questions
- 15:50Renewal Time
- 18:00Summary
- 19:40Questions
related talks
44mDistributed Locking in Kubernetes
13mLockify: Understanding Linux Distributed Lock Management Overheads in Shared Storage
21mLogDevice At Scale
48mHow to build distributed concurrency primitives
17mNear Optimal Latency Versus Cost Tradeoffs in Geo Distributed Storage
14mFast and Scalable In-network Lock Management Using Lock Fission
20mFine Grained Replicated State Machines for a Cluster Storage System
23mBodega: Localized Linearizable Reads at Anywhere Anytime via Roster Leases