Skip to content

DOCS-1632: Clarify to which size metric the limit for sharding an existi... #1226

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.

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

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
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
21 changes: 8 additions & 13 deletions source/reference/limits.txt
Original file line number Diff line number Diff line change
Expand Up @@ -149,19 +149,14 @@ Sharded Clusters

.. limit:: Sharding Existing Collection Data Size

When enabling sharding on an existing collection, MongoDB imposes a
maximum size on those collections to ensure that its possible to
create chunks. The precise size of the limitation is a function of
the chunk size and the data size: *MongoDB supports sharding all
collections smaller than 256 gigabytes.* You may be able to enable
sharding for existing collections between 256 and 400 gigabytes in
size, depending on the distribution of document sizes.

.. note::

This limitation *only* applies to sharding collections that have
existing data sets, and is *not* a limit on the size of a
sharded collection.
For existing collections, MongoDB supports enabling sharding on
collections that contain less than 256 gigabytes of data. MongoDB may
be able to shard collections with as many as 400 gigabytes depending
on the distribution of document sizes. The precise size of the
limitation is a function of the chunk size and the data size.

.. note:: Sharded collections may have *any* size, after successfully
enabling sharding.

.. limit:: Single Document Modification Operations in Sharded Collections

Expand Down