Failure semantics

Uses your system voice; voice and rate in settings.

Snapshot

≈ 1 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

In distributed computing, failure semantics is used to describe and classify errors that distributed systems can experience.

In distributed computing, failure semantics is used to describe and classify errors that distributed systems can experience.

Types of errors

A list of types of errors that can occur: An omission error is when one or more responses fails. A crash error is when nothing happens. A crash is a special case of omission when all responses fail. A Timing error is when one or more responses arrive outside the time interval specified. Timing errors can be early or late. An omission error is a timing error when a response has infinite timing error. An arbitrary error is any error, (i.e. a wrong value or a timing error). When a client uses a server it can cope with different type errors from the server. If it can manage a crash at the server it is said to assume the server to have crash failure semantics. If it can manage a service omission it is said to assume the server to have omission failure semantics. Failure semantics are the type of errors that are expected to appear. Should another type of error appear it will lead to a service failure because it cannot be managed.

References

Text derived from https://en.wikipedia.org/w/index.php?oldid=1275205408 under CC BY-SA 4.0; modifications have been made.

Provenance

snapshot enwiki-001275205408 · captured 1739293366.0 · version history

Cite this page as: encyclopegia.org, “Failure semantics”, snapshot enwiki-001275205408. https://encyclopegia.org/a/failure-semantics

Sources cited in this revision

Extracted from the cited revision's reference blocks; absent citations are not invented.