From bd55354b6bc352a14e5364ed3e74c4896b383501 Mon Sep 17 00:00:00 2001 From: Michael Goddard Date: Tue, 1 Oct 2024 14:02:32 -0400 Subject: [PATCH] Update replication-layer.md Updating so that "them" maps to "new nodes" for agreement in number --- src/current/v24.2/architecture/replication-layer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/v24.2/architecture/replication-layer.md b/src/current/v24.2/architecture/replication-layer.md index 137acbfd78c..29c86695bbe 100644 --- a/src/current/v24.2/architecture/replication-layer.md +++ b/src/current/v24.2/architecture/replication-layer.md @@ -19,7 +19,7 @@ Ensuring consistency with nodes offline, though, is a challenge many databases f The number of failures that can be tolerated is equal to *(Replication factor - 1)/2*. For example, with 3x replication, one failure can be tolerated; with 5x replication, two failures, and so on. You can control the replication factor at the cluster, database, and table level using [replication zones]({% link {{ page.version.version }}/configure-replication-zones.md %}). -When failures happen, though, CockroachDB automatically realizes nodes have stopped responding and works to redistribute your data to continue maximizing survivability. This process also works the other way around: when new nodes join your cluster, data automatically rebalances onto it, ensuring your load is evenly distributed. +When failures happen, though, CockroachDB automatically realizes nodes have stopped responding and works to redistribute your data to continue maximizing survivability. This process also works the other way around: when new nodes join your cluster, data automatically rebalances onto them, ensuring your load is evenly distributed. ### Interactions with other layers