liveness-property · also liveness (distributed systems)

Liveness property

A liveness property is an execution requirement for which every finite prefix can be extended to an execution satisfying the requirement.

Related Observatory article: Read on hesela.com

Extendability classifies the property; it does not mean an implementation may offer just one successful schedule. The implementation must satisfy its specification on every execution admitted by its model. [1]

Eventual completion supplies no numerical deadline. Finite waiting alone does not establish permanent noncompletion; a timed service requirement is a different obligation. [2]

State the progress assumptions. Paxos can retain its decision constraints while competing proposers prevent progress; its progress argument needs a suitably selected proposer, a sufficiently high proposal number and successful communication with a majority of acceptors. [3]

Relations

related
Safety property, Consensus, FLP impossibility

Citations

  1. Alpern and Schneider. Defining Liveness. Information Processing Letters 21(4), 181-185 (1985), sections 1-3. (accessed 2026-11-20)
  2. Schneider and Lamport. Another Position Paper on Fairness. Software Engineering Notes 13(3), 1988, pp. 1-2. (accessed 2026-11-20)
  3. Lamport. Paxos Made Simple (2001), sections 2.1, 2.4 and 2.5. (accessed 2026-11-20)
Sources & caveats
  • Primary-source synthesis with constructed reasoning examples, not a protocol execution, implementation certification or new proof.

JSON: /data/terms/liveness-property.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Liveness property. Hesela. 2026-11-20. https://hesela.dev/terms/liveness-property/