mirror/keycloak
1
0
Fork 0
mirror of https://github.com/keycloak/keycloak.git synced 2025-12-21 14:30:05 -06:00
Code Issues Packages Projects Releases Wiki Activity

Document network latency requirements for high available setups

Browse Source 
Closes #42186

Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
This commit is contained in:
Alexander Schwartz
2025-08-28 23:46:20 +02:00
committed by GitHub
parent a64c5c0d70
commit 1eba022149
3 changed files with 16 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/guides/high-availability/multi-cluster/building-blocks.adoc
View File

@@ -19,7 +19,9 @@ include::../partials/blueprint-disclaimer.adoc[]
== Two sites with low-latency connection
Ensures that synchronous replication is available for both the database and the external {jdgserver_name}.
{project_name} requires a low latency network connection for the synchronous replication of data by the database and the external {jdgserver_name}.
include::../partials/network-latency.adoc[]
*Suggested setup:* Two AWS Availability Zones within the same AWS Region.

10
docs/guides/high-availability/partials/network-latency.adoc Normal file
View File

@@ -0,0 +1,10 @@
////
See https://www.cloudping.co/ for an overview of AWS latencies inside of a region, for example, from eu-west-1 to eu-west-1.
The latency within a region is the latency between AZs.
////
A P50 round-trip latency of less than 5 ms is suggested and below 10 ms is strongly recommended, together with a reliable network between the zones to avoid unexpected problems with latency, throughput or connectivity.
Network latency and latency spikes amplify in the response time of the service and can lead to queued requests, timeouts, and failed requests.
Networking problems can cause downtimes until the failure detection isolates problematic nodes.

4
docs/guides/high-availability/single-cluster/building-blocks.adoc
View File

@@ -22,7 +22,9 @@ include::../partials/blueprint-disclaimer.adoc[]
[#single-cluster-blocks-low-latency]
== Multiple availability-zones with low-latency connection
Ensures that synchronous replication is available for both the database and {project_name} clustering.
{project_name} requires a low latency network connection for the synchronous replication of data by the database and {project_name} clustering.
include::../partials/network-latency.adoc[]
*Suggested setup:* A {kubernetes} cluster consisting of two or more AWS Availability Zones within the same AWS Region.