mirror of https://github.com/status-im/consul.git
docs: followup on grammar and typo for latency requirements (#13888)
This commit is contained in:
parent
45c3562477
commit
5867db4b0e
|
@ -75,11 +75,11 @@ 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
|
||||
### Maximum Latency Network requirements
|
||||
|
||||
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).
|
||||
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 (i.e. client to server RPCs, HTTP API requests, xDS proxy configuration, DNS).
|
||||
|
||||
For data sent between all Consul agents:
|
||||
For data sent between all Consul agents the following latency requirements must be met:
|
||||
|
||||
- Average RTT for all traffic cannot exceed 50ms.
|
||||
- RTT for 99 percent of traffic cannot exceed 100ms.
|
||||
|
|
Loading…
Reference in New Issue