Repository navigation
feat: expose bounded application request hints for recovery - #373
Merged
Merged
Conversation
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
1 participant
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.
Recovery currently depends on ingress log streams to identify hot tables and table-specific read failures. Add opt-in bounded application request hints to the existing HTTP middleware and an internal nonce-bound JSON endpoint, so an observer can discover demand even while a handler is still waiting.
Requests never wait for the cache. Capacity, TTL and reply bytes are bounded; dropped/truncated observations remain explicitly incomplete and recover when loss ages out. Maintenance routes do not generate their own demand. Hints retain no payload/query/record identifiers and cannot authorize merge replacement or prove progress. The endpoint does not observe ingress-only or streaming-body failures.
Validation: metrics crate unit and actual Axum middleware integration tests pass for enabled/disabled processes; Clippy passes with warnings denied. An uncontended release microbenchmark measured 1M parse+record operations in 410 ms (not a production latency claim). See the crate documentation for rollout and coverage semantics.