{
  "slug": "tied-request",
  "term": "Tied request",
  "aliases": [
    "tied requests"
  ],
  "definition": "A tied request is a duplicate request whose server coordinates with the other copy's server so that starting execution can cancel or deprioritize a still-queued counterpart.",
  "note": "The trigger is service start, not the arrival of a completed response at the client; a cancellation-message race can still allow both copies to execute. [dean]\n\nThe linked arithmetic models completion-triggered hedging, not tied-request scheduling or queue cancellation. [hesela]",
  "related": [
    "hedged-request",
    "tail-latency",
    "adaptive-replica-selection"
  ],
  "citations": [
    {
      "id": "dean",
      "title": "Dean and Barroso. The Tail at Scale. CACM 56(2), 2013, pp. 77-78. DOI: 10.1145/2408776.2408794.",
      "url": "https://www.barroso.org/publications/TheTailAtScale.pdf",
      "accessed": "2026-10-17"
    },
    {
      "id": "hesela",
      "title": "Hesela. Hedged reads: replica dependence and cancellation work, with exact synthetic examples.",
      "url": "https://hesela.com/analyses/storage-tail-slowdowns-raid-fanout/#hedged-reads",
      "accessed": "2026-10-17"
    }
  ],
  "status": "research",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-17"
}