Skip to content

Commit b6ebe8e

Browse files
Isabella SiuIsabella Siu
authored andcommitted
DOCS-11313 fix circular reference to Jumbo Chunk
1 parent d98f9d1 commit b6ebe8e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/core/sharding-data-partitioning.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -219,9 +219,9 @@ In some cases, chunks can grow beyond the :ref:`specified chunk size
219219
<sharding-chunk-size>` but cannot undergo a :ref:`split<sharding-chunk-split>`.
220220
The most common scenario is when a chunk represents a single shard key value.
221221
Since the chunk cannot split, it continues to grow beyond the chunk size,
222-
becoming a :ref:`jumbo chunk<jumbo-chunk>`. These jumbo chunks can become a
223-
performance bottleneck as they continue to grow, especially if the shard key
224-
value occurs with high :ref:`frequency<shard-key-frequency>`.
222+
becoming a jumbo chunk. These jumbo chunks can become a performance bottleneck
223+
as they continue to grow, especially if the shard key value occurs with high
224+
:ref:`frequency<shard-key-frequency>`.
225225

226226
The addition of new data or new shards can result in data distribution
227227
imbalances within the cluster. A particular shard may acquire

0 commit comments

Comments
 (0)