Route the global endpoints to exactly the zones that are fed - #271
Merged
Merged
Conversation
Add the three prod zones that were deployed but left out of the global endpoints: gcp-us-central1-a, aws-us-east-1 and gcp-us-central1. Drop aws-euc1-az1, which has served a stale index since feeding to it stopped in vespa-engine/documentation#4846 on 2026-08-26. Both global endpoints now list exactly the six zones the docsearch feed keeps current. aws-euc1-az1 stays deployed as the pseudo-row-column test zone, it just no longer takes user traffic. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
hakonhall
approved these changes
Sep 23, 2026
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
2 participants
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.
What
Adds
gcp-us-central1-a,aws-us-east-1andgcp-us-central1to both global endpoints of thedefaultinstance, and removesaws-euc1-az1. Both endpoints then list exactly the six prod zones that the docsearch feed keeps current.aws-euc1-az1stays deployed as the pseudo-row-column test zone, it just stops taking user traffic.Why
Public docs search reaches Vespa through a Lambda that proxies api.search.vespa.ai to these global endpoints, so a prod zone outside them serves no user traffic, and a routed zone that is not fed serves a stale index. The three added zones were fully deployed but never routed, and the feed has covered all of them since vespa-engine/documentation#4874.
aws-euc1-az1was the opposite case: it has been routed while unfed since vespa-engine/documentation#4846 on 2026-08-26, so some European traffic has been answered from an August index.