From b84500a9e91569682a93e8e97fcf18961e845622 Mon Sep 17 00:00:00 2001 From: S O'Donnell Date: Mon, 8 Apr 2024 16:00:40 +0100 Subject: [PATCH] Fix spelling --- docs/03-core-concepts/02-replication/05-replication-manager.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03-core-concepts/02-replication/05-replication-manager.md b/docs/03-core-concepts/02-replication/05-replication-manager.md index 3238ea527..7804ced4b 100644 --- a/docs/03-core-concepts/02-replication/05-replication-manager.md +++ b/docs/03-core-concepts/02-replication/05-replication-manager.md @@ -254,7 +254,7 @@ Due to the reduced load on a decommissioning host, it is possible to increase th When a Datanode switches to a decommissioning state, it will adjust the size of the replication supervisor thread pool higher, and if the node returns to the In Service state, it will return to the lower thread pool limit. -Similarly when scheduling commands, SCM can allocate more commands to the decommissioning host, as it should process them more quickly due to the lower load and increased threadpool. +Similarly when scheduling commands, SCM can allocate more commands to the decommissioning host, as it should process them more quickly due to the lower load and increased thread pool. ### Global Replication Command Limit