Repository navigation
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
Open
docs(api): Lava-Retries counts a cancelled hedge attempt, and name lava-hedge-triggered (MAG-3762)#66avitenzer wants to merge 2 commits into
avitenzer wants to merge 2 commits into
Conversation
…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>
AnnaR-prog
approved these changes
Oct 7, 2026
…tries-counts-hedges # Conflicts: # docs/api/directives.md
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira ticket: MAG-3762
Router change: Magma-Devs/smart-router#440 (merged 2026-10-05). It is on
mainand 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-Retrieswas "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-Addresswas "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 (Cachedfor a cache answer).lava-hedge-triggeredgets a row. It had none:truewhen a parallel hedged attempt was sent, absent otherwise, neverfalse.docs/configuration/failover/hedge.md, "Observability": one paragraph on how a hedge shows up in those three headers.Each definition was checked against
main'srpcsmartrouter_server.go: thetotalAttempts/attemptsWithoutResultcount, the stateful absorption, and the dispatch-order provider list.mkdocs build --strictpasses locally (built with the repo'srequirements.txt).🤖 Generated with Claude Code