fail-stutter · also fail-stutter fault model, fail-stutter fault tolerance

Fail-stutter

Fail-stutter is a fault-model proposal that extends fail-stop behavior with performance faults in components that still operate.

The 2001 proposal separates correctness failures from operation below a chosen performance specification. It covers hardware and software; performance can differ persistently across components or vary over time. It is not limited to repeated pauses. The authors explicitly leave full formalization and evaluation open. [1]

Fail-slow describes degraded operation; gray failure additionally requires an application to observe trouble that the system's failure observer misses. These are related concepts, not interchangeable aliases. [2] [3]

Worked example, not a device benchmark: four mirrored pairs offer logical write rates of 100, 100, 100 and 10 MB/s. Dividing a 3,100 MB payload equally takes 77.5 s (40 MB/s overall); assigning payload in proportion to those constant rates takes 10 s (310 MB/s). Both policies write the same logical bytes with mirrored copies. This idealized allocation calculation follows section 3.2; it assumes divisible work, no shared bottleneck or placement overhead, and freedom to choose placement. Existing RAID layouts need not permit it. [1] Executable arithmetic and tests accompany the worked example. [5]

Relations

related
Fail-slow, Gray failure, Fail-stop processor

Advantages

  • Separating performance from correctness permits a design to keep using slower components when its correctness contract allows. [1]

Limitations

  • The performance specification and the boundary between slow and failed are design choices, not a universal latency threshold. [1]

Citations

  1. R. H. Arpaci-Dusseau and A. C. Arpaci-Dusseau. Fail-Stutter Fault Tolerance. HotOS VIII, 2001, sections 2-3 and 5. DOI: 10.1109/HOTOS.2001.990058. (accessed 2026-11-20)
  2. Gunawi et al. Fail-Slow at Scale. FAST 2018, sections 1-3 and Table 3; 101 reports, 112 root-cause occurrences. (accessed 2026-11-20)
  3. Huang et al. Gray Failure: The Achilles' Heel of Cloud-Scale Systems. HotOS 2017, section 3.2. DOI: 10.1145/3102980.3103005. (accessed 2026-11-20)
  4. Hesela: exact-rational fail-stutter placement example, assumptions and reproducible tests (not hardware measurements). (accessed 2026-11-20)

Further reading

  1. Hesela: Fail-slow NVMe SSDs: what SMART and heartbeats miss (accessed 2026-11-20)
Sources & caveats
  • Source synthesis of the cited papers; the arithmetic is an idealized constructed example, not an implementation or performance measurement.
  • The year identifies the HotOS VIII publication, not the first observation of performance faults.

JSON: /data/terms/fail-stutter.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Fail-stutter. Hesela. 2026-11-20. https://hesela.dev/terms/fail-stutter/