Data Systems
safety vs liveness
nothing-bad-ever vs something-good-eventually
Source board
This definition comes from the board below. Open it to see the term in context.
When Machines FailData SystemsMore terms from this board
- BFTtolerating it
- Byzantine faulta node that lies/acts arbitrarily
- clock skew/driftclocks disagree/wander
- fencing tokena rising number the resource checks to reject stale holders
- leasea time-limited lock
- logical clockorder by causality not time (Lamport/version vector)
- partial failuresome parts broken, others fine
- process pausea thread frozen mid-run (GC, VM, paging)
- system modeltiming + failure assumptions
- time-of-day vs monotonic clockwall time (can jump) vs forward-only elapsed
- timeoutthe only failure detector
- TrueTimeclock as an interval
- unbounded delayno ceiling on network latency