From 57863093565c7e23163eb2205e751f5e652139e0 Mon Sep 17 00:00:00 2001 From: David Yu Date: Mon, 25 Jul 2022 11:02:31 -0700 Subject: [PATCH] docs: add details around Consul latency requirements (#13881) * docs: add details around Consul latency requirements --- website/content/docs/agent/index.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/website/content/docs/agent/index.mdx b/website/content/docs/agent/index.mdx index 0a4ba38aa4..13e4599dce 100644 --- a/website/content/docs/agent/index.mdx +++ b/website/content/docs/agent/index.mdx @@ -75,6 +75,15 @@ Refer to the following sections for information about host, port, memory, and ot The [Datacenter Deploy tutorial](https://learn.hashicorp.com/tutorials/consul/reference-architecture?in=consul/production-deploy#deployment-system-requirements) contains additional information, including licensing configuration, environment variables, and other details. +### Maximum Latency Network requiremenmts + +Consul uses the gossip protocol to share information across agents. To function properly, you cannot exceed the protocol’s maximum latency threshold. The latency threshold is calculated according to the total round trip time (RTT) for communication between all agents. Other network usages outside of Gossip are not bound by these latency requirements (client to server RPCs, HTTP API requests, xDS proxy configuration, DNS). + +For data sent between all Consul agents: + +- Average RTT for all traffic cannot exceed 50ms. +- RTT for 99 percent of traffic cannot exceed 100ms. + ## Starting the Consul Agent Start a Consul agent with the `consul` command and `agent` subcommand using the following syntax: