# Murat Demirbas - LeaseGuard: Raft Leases Done Right (Highlights) .jpeg) ## Highlights - Besides, lease protocols have never been specified in detail, for either Raft or Paxos. For all these reasons, many Raft implementations don't use leases at all, or their [leases](https://github.com/etcd-io/raft/issues/166) [are](https://github.com/hashicorp/raft/issues/108) [buggy](https://aphyr.com/posts/316-jepsen-etcd-and-consul). ([View Highlight](https://read.readwise.io/read/01kcxmq2n66kth3ja9xzzdqfqq)) ^968174736 - Our main innovation is to rely on Raft-specific guarantees to design a simpler lease protocol that recovers faster from a leader crash. ([View Highlight](https://read.readwise.io/read/01kcxmr4g600p6cqg756krz5dt)) ^968174754 - LeaseGuard does not use extra messages or variables for lease management, and does not interfere with voting or elections. ([View Highlight](https://read.readwise.io/read/01kcxmy8akqehmnvnwfer2ncjm)) ^968174906 - In LeaseGuard, **the log is the lease**. Committing a log entry grants the leader a lease that lasts until a timeout expires. ([View Highlight](https://read.readwise.io/read/01kcxmz2h5zxgssgw852v8e33r)) ^968174920 - When a new leader L1 is elected, it checks its own log for the previous leader L0's last entry, to infer how long to wait for L0's lease to expire. ([View Highlight](https://read.readwise.io/read/01kcxmzt3aat1qc0kmag2e2n0b)) ^968174945