Skip to content

Commit 4a33a85

Browse files
committed
docs: clarify retry strategy for endpoint failures
Signed-off-by: Pavel Shukhman <[email protected]>
1 parent 8d13d59 commit 4a33a85

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

discovery/readme.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -249,9 +249,10 @@ status code with a response describing the error.
249249
If the DNS record for the discovery endpoint cannot be resolved by the client, or
250250
the discovery endpoint fails with 5xx error code, or the TLS certificate cannot be validated,
251251
the client MUST retry the discovery endpoint with the next endpoint in the list, if another
252-
endpoint is present. If no other endpoint is available, the client MUST retry the discovery
253-
endpoint with the first endpoint in the list. The client SHOULD implement an exponential
254-
backoff strategy for retries.
252+
endpoint is present. While doing so the client SHOULD preserve the priority order if provided
253+
(from highest to lowest priority). If no other endpoint is available, the client MUST retry
254+
the discovery endpoint with the first endpoint in the list. The client SHOULD implement an
255+
exponential backoff strategy for retries.
255256

256257
TODO: Handle Auth errors (401, 403) and corresponding messages.
257258

0 commit comments

Comments
 (0)