From 6c95ba38e53a5f28b0babbeba1d771e005cce27a Mon Sep 17 00:00:00 2001 From: Konstantin Dorichev <6565761+kdorichev@users.noreply.github.com> Date: Wed, 22 Oct 2025 19:18:37 +0300 Subject: [PATCH] Fix `internal_replication` value The `internal_replication` value is left `false` by default since only one replica per shard in this configuration. --- .../replication-sharding-examples/02_2_shards_1_replica.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment-guides/replication-sharding-examples/02_2_shards_1_replica.md b/docs/deployment-guides/replication-sharding-examples/02_2_shards_1_replica.md index 53ad1cb565c..09dee621d8e 100644 --- a/docs/deployment-guides/replication-sharding-examples/02_2_shards_1_replica.md +++ b/docs/deployment-guides/replication-sharding-examples/02_2_shards_1_replica.md @@ -274,7 +274,7 @@ template for distributed DDL queries, which are queries that execute across the cluster using the `ON CLUSTER` clause. By default, distributed DDL queries are allowed, but can also be turned off with setting `allow_distributed_ddl_queries`. -`internal_replication` is set to true so that data is written to just one of the replicas. +`internal_replication` is left set to false by default since only one replica per shard. ```xml