Repository navigation
cache: Wait for the proxy before the first request - #1600
Merged
Merged
Conversation
phlax
force-pushed
the
cache-wait
branch
2 times, most recently
from
November 1, 2026 15:43
bec83a5 to
ef8288c
Compare
The first request fired as soon as compose returned; front-envoy was one second old and still loading clusters, so curl got a connection reset (exit 56). Probe the never-cached private response until the proxy answers, so the first cacheable request is still served by the origin. Signed-off-by: Ryan Northey <ryan@synca.io>
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.
The first request fires as soon as compose returns, which is when the backends are healthy, not when the proxy is listening. In https://github.com/envoyproxy/envoy/actions/runs/41313931262/job/124878023013 front-envoy was one second old and still loading clusters when curl connected, so it got a connection reset (exit 56).
Probe the never-cached
privateresponse withwait_foruntil the proxy answers, so the first cacheable request is still served by the origin and the later private checks are unaffected. Same pattern as the opentelemetry example.