Failure transparency

Uses your system voice; voice and rate in settings.

Snapshot

≈ 3 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 a distributed system, failure transparency refers to the extent to which errors and subsequent recoveries of hosts and services within the system are invisible to users and applications. For example, if a server fails, but users are automatically redirected to another server and never notice the failure, the system is said to exhibit high failure transparency. Failure transparency is one of the most difficult types of transparency to achieve since it is often difficult to determine whether a server has actually failed, or whether it is simply responding very slowly. Additionally, it is generally impossible to achieve full failure transparency in a distributed system since networks are unreliable. There is also usually a trade-off between achieving a high level of failure transparency and maintaining an adequate level of system performance. For example, if a distributed system attempts to mask a transient server failure by having the client try to contact the failed server multiple times, performance of the system may be negatively affected. In this case, it would have been preferable to have given up earlier and tried another server.

In a distributed system, failure transparency refers to the extent to which errors and subsequent recoveries of hosts and services within the system are invisible to users and applications. For example, if a server fails, but users are automatically redirected to another server and never notice the failure, the system is said to exhibit high failure transparency. Failure transparency is one of the most difficult types of transparency to achieve since it is often difficult to determine whether a server has actually failed, or whether it is simply responding very slowly. Additionally, it is generally impossible to achieve full failure transparency in a distributed system since networks are unreliable. There is also usually a trade-off between achieving a high level of failure transparency and maintaining an adequate level of system performance. For example, if a distributed system attempts to mask a transient server failure by having the client try to contact the failed server multiple times, performance of the system may be negatively affected. In this case, it would have been preferable to have given up earlier and tried another server.

See also

Byzantine fault tolerance Intrusion Tolerance Capillary routing Cluster (computing) Data redundancy Elegant degradation Error detection and correction Fail-safe Fault-tolerant design Fault-tolerant system Progressive Enhancement Separation of protection and security Transparency (computing)

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

Provenance

snapshot enwiki-001266063240 · captured 1735508854.0 · version history

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

Sources cited in this revision

No external citation was extracted for this revision. That is a statement about the source, not a claim that none exists.