Skip to content

docs(api): Lava-Retries counts a cancelled hedge attempt, and name lava-hedge-triggered (MAG-3762) - #66

Open
avitenzer wants to merge 2 commits into
mainfrom
docs/mag-3762-lava-retries-counts-hedges
Open

avitenzer wants to merge 2 commits into
mainfrom
docs/mag-3762-lava-retries-counts-hedges

Conversation

@avitenzer

Copy link
Copy Markdown
Contributor

Jira ticket: MAG-3762

Router change: Magma-Devs/smart-router#440 (merged 2026-10-05). It is on main and not yet in a release, so merge this with or after the release that carries #440.

What changes

  • docs/api/directives.md, "Response headers":
    • Lava-Retries was "Number of retry attempts made for this relay", which can't say whether an attempt the router sent and then cancelled counts. It now gives the contract ruled in MAG-1818 and restored by #440: attempts beyond the first that the router sent, including a hedged attempt it cancelled because another node answered first. The header is absent when the request took one attempt, and a write's fan-out reports none.
    • Lava-Provider-Address was "the node that ultimately served the response". On a multi-attempt request it lists every node tried, in dispatch order, with the one that answered last (Cached for a cache answer).
    • lava-hedge-triggered gets a row. It had none: true when a parallel hedged attempt was sent, absent otherwise, never false.
  • docs/configuration/failover/hedge.md, "Observability": one paragraph on how a hedge shows up in those three headers.

Each definition was checked against main's rpcsmartrouter_server.go: the totalAttempts / attemptsWithoutResult count, the stateful absorption, and the dispatch-order provider list.

mkdocs build --strict passes locally (built with the repo's requirements.txt).

🤖 Generated with Claude Code

…va-hedge-triggered (MAG-3762)

The response-header table defined Lava-Retries only as "number of retry
attempts made", which cannot say whether an attempt the router sent and
then cancelled counts. Since smart-router #440 it does, per MAG-1818:
every attempt beyond the first, including a hedge loser still running
when the winner answered; a write's fan-out reports none.

Lava-Provider-Address said "the node that ultimately served the
response", but on a multi-attempt request it lists every node tried, in
dispatch order, with the server last ("Cached" for a cache answer).

lava-hedge-triggered had no row at all. Add it, and say on the Hedge
page how a hedge shows up in the three headers.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…tries-counts-hedges

# Conflicts:
#	docs/api/directives.md

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants