From b88a7eee95b89d4a53d2e1f5ccfa1679a6197fce Mon Sep 17 00:00:00 2001 From: James Phillips Date: Thu, 9 Feb 2017 20:28:38 -0800 Subject: [PATCH] Adds clarifying note about the wakeup jitter. Closes #2727. --- website/source/docs/agent/http.html.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/source/docs/agent/http.html.markdown b/website/source/docs/agent/http.html.markdown index e922be765..445d00eca 100644 --- a/website/source/docs/agent/http.html.markdown +++ b/website/source/docs/agent/http.html.markdown @@ -45,7 +45,10 @@ to wait for any changes subsequent to that index. In addition to `index`, endpoints that support blocking will also honor a `wait` parameter specifying a maximum duration for the blocking request. This is limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This value can be specified -in the form of "10s" or "5m" (i.e., 10 seconds or 5 minutes, respectively). +in the form of "10s" or "5m" (i.e., 10 seconds or 5 minutes, respectively). A small random +amount of additional wait time is added to the supplied maximum `wait` time to spread out +the wake up time of any concurrent requests. This adds up to `wait / 16` additional time +to the maximum duration. A critical note is that the return of a blocking request is **no guarantee** of a change. It is possible that the timeout was reached or that there was an idempotent write that does