From 5d3ec9a793b7d1bc051699778a3a9c830c138b3b Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Thu, 21 Sep 2023 22:51:48 -0400 Subject: [PATCH] Fix bad link --- docs/architecture/georedundancy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/georedundancy.md b/docs/architecture/georedundancy.md index b8ac913..8a328b9 100644 --- a/docs/architecture/georedundancy.md +++ b/docs/architecture/georedundancy.md @@ -40,7 +40,7 @@ Thus, in this design, several normally-possible recovery situations become harde ## Network Speed -PVC clusters are quite network-intensive, as outlined in the [hardware requirements](hardware-requirements.md##networking) documentation. This can pose problems with multi-site clusters with slower interconnects. At least 10Gbps is recommended between nodes, and this includes nodes in different physical locations. In addition, the traffic here is bursty and dependent on VM workloads, both in terms of storage and VM migration. Thus, the site interconnects must account for the speed required of a PVC cluster in addition to any other traffic. +PVC clusters are quite network-intensive, as outlined in the [hardware requirements](hardware-requirements.md#networking) documentation. This can pose problems with multi-site clusters with slower interconnects. At least 10Gbps is recommended between nodes, and this includes nodes in different physical locations. In addition, the traffic here is bursty and dependent on VM workloads, both in terms of storage and VM migration. Thus, the site interconnects must account for the speed required of a PVC cluster in addition to any other traffic. ## Network Latency & Distance