From 9c8c0f485ba06433bc159adcc78cf9fae04bd88b Mon Sep 17 00:00:00 2001 From: Edward Huang Date: Wed, 21 Aug 2024 22:40:49 -0700 Subject: [PATCH] clarify uplink polling --- docs/source/managed-federation/uplink.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/managed-federation/uplink.mdx b/docs/source/managed-federation/uplink.mdx index 53c1ac490..de11c20b6 100644 --- a/docs/source/managed-federation/uplink.mdx +++ b/docs/source/managed-federation/uplink.mdx @@ -35,13 +35,13 @@ To maximize uptime, Uplink is hosted simultaneously at two endpoints, one in GCP ### GraphOS Router -If you use the GraphOS Router with managed federation, by default it polls Uplink every ten seconds. Every time it does so, it cycles through Uplink endpoints in round-robin fashion. +If you use the GraphOS Router with managed federation, by default it polls Uplink every ten seconds. Every time it does so, it cycles through the list of Uplink URLs in order until it gets a successful response. Whenever a poll request times out or otherwise fails (the default timeout is thirty seconds), the router continues polling as usual at the next interval. In the meantime, it continues using its most recent successfully obtained configuration. ### `@apollo/gateway` -If you use the `@apollo/gateway` library with managed federation, by default your gateway polls Uplink every ten seconds. Every time it does so, it cycles through Uplink endpoints in round-robin fashion. +If you use the `@apollo/gateway` library with managed federation, by default your gateway polls Uplink every ten seconds. Every time it does so, it cycles through the list of Uplink URLs in order until it gets a successful response.