Skip to content

Commit 1fd9ce8

Browse files
author
Bob Grabar
committed
DOCS-983 splitting chunks review edits
1 parent 2f65486 commit 1fd9ce8

File tree

4 files changed

+15
-32
lines changed

4 files changed

+15
-32
lines changed
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
.. warning::
2+
3+
Be careful when splitting chunks. When you shard a collection that
4+
has existing data, MongoDB automatically creates chunks to evenly
5+
spread the collection. Performing additional splits requires
6+
knowledge of the resulting chunk sizes by numbers of documents and by
7+
size. You do not want splits that cause some chunks to be much larger
8+
than others. This leads to balancing based on count of chunks, not on
9+
their size, which may cause extreme load/data-distribution problems.

source/reference/command/split.txt

Lines changed: 4 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -12,20 +12,10 @@ split
1212
this command makes it possible for administrators to manually
1313
create splits.
1414

15-
In normal operation there is no need to manually split chunks. The
16-
:term:`balancer` and other sharding infrastructure will automatically
17-
create chunks in the course of normal operations. See
18-
:doc:`/core/sharded-cluster-internals` for more information.
19-
20-
.. warning::
21-
22-
Be careful when splitting chunks. When you shard a collection that
23-
has existing data, MongoDB automatically creates chunks to evenly
24-
spread the collection. Performing additional splits requires
25-
knowledge of the resulting chunk sizes by numbers of documents and by
26-
size. You do not want splits that cause some chunks to be much larger
27-
than others. This leads to balancing based on count of chunks, not on
28-
their size, which may cause extreme load/data-distribution problems.
15+
In most clusters, MongoDB will manage all chunk creation and
16+
distribution operations without manual intervention.
17+
18+
.. include:: /includes/warning-splitting-chunks.rst
2919

3020
Consider the following example:
3121

source/reference/command/splitChunk.txt

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,6 @@ splitChunk
1010
:method:`sh.splitFind()` and :method:`sh.splitAt()` functions in the
1111
:program:`mongo` shell to access this functionality.
1212

13-
.. warning::
14-
15-
Be careful when splitting chunks. When you shard a collection that
16-
has existing data, MongoDB automatically creates chunks to evenly
17-
spread the collection. Performing additional splits requires
18-
knowledge of the resulting chunk sizes by numbers of documents and by
19-
size. You do not want splits that cause some chunks to be much larger
20-
than others. This leads to balancing based on count of chunks, not on
21-
their size, which may cause extreme load/data-distribution problems.
13+
.. include:: /includes/warning-splitting-chunks.rst
2214

2315
.. admin-only.

source/tutorial/manage-chunks-in-sharded-cluster.txt

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -58,15 +58,7 @@ You may want to split chunks manually if:
5858
values between ``300`` and ``400``, *but* all values of your shard
5959
keys are between ``250`` and ``500`` are in a single chunk.
6060

61-
.. warning::
62-
63-
Be careful when splitting chunks. When you shard a collection that
64-
has existing data, MongoDB automatically creates chunks to evenly
65-
spread the collection. Performing additional splits requires
66-
knowledge of the resulting chunk sizes by numbers of documents and by
67-
size. You do not want splits that cause some chunks to be much larger
68-
than others. This leads to balancing based on count of chunks, not on
69-
their size, which may cause extreme load/data-distribution problems.
61+
.. include:: /includes/warning-splitting-chunks.rst
7062

7163
Use :method:`sh.status()` to determine the current chunks ranges across
7264
the cluster.

0 commit comments

Comments
 (0)