From b6ebe8e76f1a9ff6d5b915b78a92a0f2766a9916 Mon Sep 17 00:00:00 2001 From: Isabella Siu Date: Fri, 12 Oct 2018 10:11:07 -0400 Subject: [PATCH] DOCS-11313 fix circular reference to Jumbo Chunk --- source/core/sharding-data-partitioning.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/core/sharding-data-partitioning.txt b/source/core/sharding-data-partitioning.txt index 8b9dbfa6727..2841360599e 100644 --- a/source/core/sharding-data-partitioning.txt +++ b/source/core/sharding-data-partitioning.txt @@ -219,9 +219,9 @@ In some cases, chunks can grow beyond the :ref:`specified chunk size ` but cannot undergo a :ref:`split`. The most common scenario is when a chunk represents a single shard key value. Since the chunk cannot split, it continues to grow beyond the chunk size, -becoming a :ref:`jumbo chunk`. These jumbo chunks can become a -performance bottleneck as they continue to grow, especially if the shard key -value occurs with high :ref:`frequency`. +becoming a jumbo chunk. These jumbo chunks can become a performance bottleneck +as they continue to grow, especially if the shard key value occurs with high +:ref:`frequency`. The addition of new data or new shards can result in data distribution imbalances within the cluster. A particular shard may acquire