Repository navigation
docs(api): lava-relay-timeout is bounded between 300ms and the call's own budget (MAG-3600) - #62
Merged
Merged
Conversation
8 of 12 tasks
AnnaR-prog
approved these changes
Oct 7, 2026
AnnaR-prog
changed the base branch from
docs/mag-3988-relay-timeout-non-positive
to
main
October 7, 2026 11:17
… own budget (MAG-3600) smart-router#427 stops using the lava-relay-timeout header verbatim. A value under 300ms is raised to 300ms (still below --min-relay-timeout, so callers can hedge sooner than the floor), and a value above the request's own budget, the budget it gets with no header, is held to that budget unless the operator sets the new --max-caller-relay-timeout. A value at or above the own budget turns hedging off for that request. The reply carries Lava-Relay-Timeout-Applied with the window used. directives.md and failover/timeout.md promised "verbatim" and that 100ms yields 100ms; both now describe the bounds, the hedging trade-off and the reply header. cli.md gains the new flag. retry.md and failover/index.md mention the header only generically and stay correct. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
AnnaR-prog
force-pushed
the
docs/mag-3600-relay-timeout-bounds
branch
from
October 7, 2026 11:48
08a53d2 to
eee339b
Compare
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-3600
Router change: Magma-Devs/smart-router#427. Merge after it (and after #54, which this stacks on), since until #427 ships the header is still used as sent.
What changes
docs/api/directives.md, "Override the per-attempt timeout": the "used verbatim" promise is gone. The section now gives the bounds:300msbecomes300ms. That is still below--min-relay-timeout, so a client can still hedge sooner than the floor;--max-caller-relay-timeout.A value at or above that budget turns hedging off for the request. "When to use" no longer recommends the header for pushing slow methods past their budget.
docs/api/directives.md, "Response headers": new row forLava-Relay-Timeout-Applied, the per-attempt timeout the router actually used. It is sent only when the request carriedlava-relay-timeout.docs/configuration/failover/timeout.md: the header-override section becomes a table of value → timeout used, plus the own-budget definition, the hedging trade-off and the reply header. The heavydebug_*tuning row now points to--max-caller-relay-timeoutfor anything beyond the method's budget. The "100msyields100ms" pitfall now says300ms, and a new pitfall covers a value above the budget.docs/reference/cli.md: new row for--max-caller-relay-timeout(default0: callers cannot extend a request's budget).retry.mdandfailover/index.mdmention the header only in general terms and stay correct.mkdocs build --strictpasses locally (built with the repo'srequirements.txt).🤖 Generated with Claude Code