{
  "slug": "timing-failure",
  "term": "Timing failure",
  "aliases": [
    "timing fault"
  ],
  "definition": "A timing failure occurs when a service gives a functionally correct response outside the time interval required by its specification.",
  "note": "Cristian's classification includes early and late responses; a response covers required state transitions as well as outputs. Classify behavior at a named service boundary. A late result is not the same observation as permanent nonresponse, and other omission models can abstract a receive timeout differently. [cristian-timing]\n\nA caller-selected waiting limit is not automatically the service's timing specification. Dwork, Lynch and Stockmeyer reject classifying processors as faulty merely because messages exceed an arbitrarily chosen delay bound. Partial synchrony can assume unknown bounds, or bounds that hold only after an unknown stabilization time; neither assumption alone supplies an unconditional per-request completion deadline. [dls-timing]\n\nExpiration of a wait also need not end associated work. Linux completion documentation requires the completion object's memory to remain valid until related activity finishes, even after a timed wait returns. Its interruptible timed wait returns a positive value for completion, zero for timeout and -ERESTARTSYS for signal interruption. Preserve all three outcomes in a signed long. These synchronization results do not establish storage cancellation or persistence. [linux-completion-lifetime]",
  "related": [
    "io-timeout",
    "partial-synchrony"
  ],
  "citations": [
    {
      "id": "cristian-timing",
      "title": "Cristian. Understanding Fault-Tolerant Distributed Systems. CACM 34(2), 56-78, 1991; Failure Classification and Failure Semantics, pp. 58-60.",
      "url": "https://eecs.wsu.edu/~bakken/562-files/cristian-ftds-CACM91.pdf",
      "accessed": "2026-11-20"
    },
    {
      "id": "dls-timing",
      "title": "Dwork, Lynch and Stockmeyer. Consensus in the Presence of Partial Synchrony. JACM 35(2), 288-323, 1988; section 1.2.",
      "url": "https://groups.csail.mit.edu/tds/papers/Lynch/jacm88.pdf",
      "accessed": "2026-11-20"
    },
    {
      "id": "linux-completion-lifetime",
      "title": "Linux kernel documentation: Completions, Initializing completions and timed waits.",
      "url": "https://docs.kernel.org/scheduler/completion.html",
      "accessed": "2026-11-20"
    }
  ],
  "status": "unknown",
  "advantages": [],
  "limitations": [
    {
      "text": "A timeout alone does not identify a failed component or establish non-execution, data loss or safe retry.",
      "citationIds": [
        "cristian-timing",
        "linux-completion-lifetime"
      ]
    }
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-20",
  "provenance": [
    "Primary-source synthesis of service timing semantics, not a new failure detector or a measured storage latency distribution."
  ]
}
