From 0f1735634d1f9d522be336bc302a4684728dab67 Mon Sep 17 00:00:00 2001 From: Pierre Souchay Date: Sun, 1 Jul 2018 23:37:40 +0200 Subject: [PATCH] Improve doc for async-cache --- website/source/docs/agent/options.html.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/source/docs/agent/options.html.md b/website/source/docs/agent/options.html.md index 65402c2caf..06f071dd04 100644 --- a/website/source/docs/agent/options.html.md +++ b/website/source/docs/agent/options.html.md @@ -500,9 +500,10 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass policy for a token cannot be read from the [`acl_datacenter`](#acl_datacenter) or leader node, the down policy is applied. In "allow" mode, all actions are permitted, "deny" restricts all operations, and "extend-cache" allows any cached ACLs to be used, ignoring their TTL - values. If a non-cached ACL is used, "extend-cache" acts like "deny". "async-cache" acts the same - way as "extend-cache" but performs updates asynchronously when ACL is present but its TTL is - expired. + values. If a non-cached ACL is used, "extend-cache" acts like "deny". + The value "async-cache" acts the same way as "extend-cache" but performs updates + asynchronously when ACL is present but its TTL is expired, thus, if latency is bad between + ACL authoritative and other datacenters, latency of operations is not impacted. * `acl_agent_master_token` - Used to access agent endpoints that require agent read