Skip to content

DOCS-11313 fix circular reference to Jumbo Chunk #3448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 12, 2018
Merged

DOCS-11313 fix circular reference to Jumbo Chunk #3448

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/core/sharding-data-partitioning.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -219,9 +219,9 @@ In some cases, chunks can grow beyond the :ref:`specified chunk size
<sharding-chunk-size>` but cannot undergo a :ref:`split<sharding-chunk-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<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<shard-key-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<shard-key-frequency>`.

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